Related
THIS OP IS OUTDATED! WIP!
Hello everybody!
You might or might not have already heard of MultiROM, THE multi-boot mod for the Nexus 7. I have recently found it and have decided to port it for our device.
First of all, it is a very initial release now. Though I have tested multiple cases and didn't find any problem except those in the bug list, bugs can arise. Do have a backup! Also, do read through the whole OP and 2nd post! If you don't understand something, rather read again and/or ask!
For more information on how it works and what it does, I suggest that you read the first few posts in the original thread. Those are very detailed and well-written posts that explain MultiROM in general. Installing roms to USB and Ubuntu/Ubuntu Touch of course doesn't work for our device atm.
Installation
The device must not be encrypted!
You need to flash the modified TWRP recovery that has MultiROM extensions. My version is based on the latest sources with gordon0001's device-specific modifications included. You can keep this recovery if you don't want to use MultiROM anymore and you like TWRP, because the MultiROM extensions don't interfere with other functions, even if the boot sector is not injected.
You have to flash a kernel that is capable of Kexec-hardboot. I compiled iodak's v07 CM kernel and official CM kernel with the patch, choose one of them. I have noticed an approx. 3 sec. vibration at boot with iodak, that's why I have included official CM kernel too.
Finally you have to flash MultiROM.
Links
You can find everything at http://d-h.st/users/Adam77Root/?fld_id=22980#files.
MultiROM_TWRP_X3.zip: The modified TWRP recovery from latest sources with gordon0001's device-specific changes and MultiROM support.
CM_kernel_patched.zip and iodakX3_v07CM_patched.zip: Official and iodak CM kernels with Kexec-hardboot patch.
iodakX3_v07_patched.zip: iodak stock kernel with Kexec-hardboot patch.
MultiROM_P880_v12.zip: The actual MultiROM package. Contains the latest version of Trampoline (the init binary of the system) and MultiROM binaries with all the needed device-specific changes. Even Pong works pretty smooth.
x3_hardboot.diff: Kexec-hardboot patch for 3.1.10 kernel.
mrom_p880.patch: Device-specific changes for Trampoline and MultiROM.
ui.xml: UI layout definition for TWRP for 720x1280 screens with MultiROM additions.
Known bugs
Reboot to recovery doesn't work.
USB tab doesn't do anything. This is because USB host mode (OTG) doesn't work on our device. Will reach out to kholk regarding this.
Sometimes in landscape mode, the default selected rom gets booted on the first touch. This is yet to be investigated.
Changelog
14 August 2013: Initial release
Credits
@Tasssadar for MultiROM, Kexec-hardboot for Nexus 7 and his help with debugging and porting
@mkasick for original Kexec-hardboot implementation
@iodak for his kernel
@gordon0001 for the device-specific TWRP modifications
Every custom modification to devices have risks. Flash these at your own risk!
Have fun and enjoy!
General use
Some notes and instructions regarding general use
For now, I have only provided patched 4.2.2 CM kernels. This means, you have to be on CM or CM-based rom with Android version 4.2.2. Don't try it with stock at the moment in any way. It won't work, but is on the to-do list. As Kexec-hardboot will reach out to devs, it will be supported in every rom ultimately.
In the next two examples, I will refer any official, unofficial, or CM-based roms as CM. Keep this in mind.
I use the word 'injected', because MultiROM is actually injected into the boot partition. It works on any kernel that is capable of doing Kexec-hardboot (and if you don't want to use different kernel (i.e. you will use kernel sharing), it will work on unpatched kernels as well).
I may refer to non-shared kernel method as Kexec(-hardboot) method.
Example scenario of multi-booting CM with CM and kernel sharing
You are on CM with MultiROM-capable recovery, patched kernel and MultiROM-injected and you want to install e.g. CarbonRom as second.
Boot into TWRP, navigate to Advanced->MultiROM and select 'Add ROM'. Since the base rom is CM, you can share the same kernel. It will be faster as there will be no hardboot needed.
The installation steps are easy and it doesn't take more time than a normal installation.
Example scenario of multi-booting CM with CM and different kernel
You are on CM with MultiROM-capable recovery, patched kernel and MultiROM-injected and you want to install e.g. CarbonRom as second.
Boot into TWRP, navigate to Advanced->MultiROM and select 'Add ROM'. Select 'Don't share'.
Continue with installation.
Now, since the target kernel (that is installed with the rom) is very likely not patched, you will have to flash one of my linked kernels to that rom. Do this by selecting 'List roms', selecting the desired rom, than 'Flash ZIP' and flashing one of the kernels I have patched.
You can only share the kernels between the same Android version (i.e. stock base->only stock rom can use shared kernel, 4.2 base->only 4.2 rom can use shared kernel, 4.3 base->only 4.3 rom can use shared kernel, etc.), but this is not the case with the Kexec method. Just keep in mind that for example even if your base rom is CM, for a stock secondary rom you have to flash a stock patched kernel.
The build
Some notes about the build
x3_hardboot.diff: This is the Kexec-hardboot patch for the 3.1.10 kernel. Since it is needed for target kernels as well, I would like to reach out in this post to @arararagi, @demetris_I, @iodak, @kholk, @laufersteppenwolf and @Pesach85 (in no particular order, this is how your threads are in order in Original Android Development forum right now). I and fellow users would be grateful if you could include the patch in the kernel so they can be used as both host and target kernels as well. UPDATE: It doesn't reserve one more megabyte before ram_console from now on.
mrom_p880.patch: This contains all the device-specific patches that are needed to get MultiROM booting and working on the P880. It is built on top of the latest git changes as of today. It also contains some comments about multiple devices compatibility, those are reminders for Tasssadar.
ui.xml: UI layout definition for TWRP for 720x1280 screens with MultiROM additions. Needs to be put into TWRPdir/gui/devices/720x1280/res/. The recovery I have created is based on the latest MultiROM TWRP with @gordon0001's device-specific changes.
You can find links to the upstream MultiROM and MultiROM TWRP in the original thread.
Simply incredible!!! :thumbup:thanks a lot man. I always wanted to try dualboot
Sent from my LG-P880 using xda premium
Awaiting the Patched Stock Kernel to dual boot stock and AOSP Good Work man, hopefully @iodak will be able to patch his kernel by today so i can get modding :3
Nice work man! I have also seen hardboot kernels in the N7 section, but got into the hospital then....
But i will include it for sure when i'm back home
Sent from my Nexus 7 using XDA Premium HD app
tnx for your very nice work
how i can flash twrp ?
i want to flash it on cwm but i cant
edite : thats my fault i am so sorry
penguin449 said:
Awaiting the Patched Stock Kernel to dual boot stock and AOSP Good Work man, hopefully @iodak will be able to patch his kernel by today so i can get modding :3
Click to expand...
Click to collapse
If anybody won't be faster, I will provide it tomorrow.
laufersteppenwolf said:
Nice work man! I have also seen hardboot kernels in the N7 section, but got into the hospital then....
But i will include it for sure when i'm back home
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks! Take your time, rest and get better!
Sent from my LG-P880
Adam77Root said:
If anybody won't be faster, I will provide it tomorrow.
Sent from my LG-P880
Click to expand...
Click to collapse
Don't get me wrong, i would be more then Happy to do it myself, however till my new PC Arrives i wont be able to use a Linux Distro for some time, if there's a method to do this on windows (Natively, can't even run anything in VM's) then point me in the right direction! Sorry for the inconvenience!
penguin449 said:
Don't get me wrong, i would be more then Happy to do it myself, however till my new PC Arrives i wont be able to use a Linux Distro for some time, if there's a method to do this on windows (Natively, can't even run anything in VM's) then point me in the right direction! Sorry for the inconvenience!
Click to expand...
Click to collapse
I didn't get you wrong buddy. I have no problems with making a stock version, just didn't have time for that today.
Sent from my LG-P880
giantic hack
ohhh well the one big giantic hack is coming to our O4X! that`s very nice
thank you for this port and thank you for your fast work? tomorrow with stock and on saturday with android 4.3 ?
Donation sent
Whaaaaaattt?
Just were browsing N7 forum few days ago and saw MultiROM and thought "Ahh these lucky nexus guys, I wanna have it to! " and here we go hahahah
Sent from my OptimusX4HD using xda app-developers app
how can install rom to ext-sd ?
in next version can we have stock rom and miui rom or other custom rom?
tnx
Hey guys, heres iodak stock kernel with kexec patch: https://www.dropbox.com/s/ko752pu1akuvfzh/iodakX3_v07-realms.zip
Btw i theres a problem with the twrp zip package, im gonna try fastboot flash it. Has anyone had success?
Say Whut?
@Adam77Root, you just made me wanna flashing and flashing and flashing one day before I go into vacation, I will try to get some time today and test it!
Thanks so much!
Afro said:
Say Whut?
Adam77Root, you just made me wanna flashing and flashing and flashing one day before I go into vacation, I will try to get some time today and test it!
Thanks so much!
Click to expand...
Click to collapse
You can flash 10 different roms and play with them over your vacation. Thats what vacations are right?
Hehe @JoinTheRealms , you understand me
Wow, I just saw your Iodak Stock Kernel with Kexec patch, verrry nice, now I can use Stock ROMs, too!
Did you already test it?
JoinTheRealms said:
Donation sent
Click to expand...
Click to collapse
Thanks very much!
m.homauon said:
how can install rom to ext-sd ?
in next version can we have stock rom and miui rom or other custom rom?
tnx
Click to expand...
Click to collapse
You can't install to external SD. It could be modified to allow it, but there would be a huge performance decrease. Literally, roms would be lagging too much.
JoinTheRealms said:
Hey guys, heres iodak stock kernel with kexec patch: https://www.dropbox.com/s/ko752pu1akuvfzh/iodakX3_v07-realms.zip
Btw i theres a problem with the twrp zip package, im gonna try fastboot flash it. Has anyone had success?
Click to expand...
Click to collapse
Just was about to reply to your PM.
What kind of problem is with the zip package?
I will update the first posts in the afternoon.
Afro said:
Hehe @JoinTheRealms , you understand me
Wow, I just saw your Iodak Stock Kernel with Kexec patch, verrry nice, now I can use Stock ROMs, too!
Did you already test it?
Click to expand...
Click to collapse
Nah i couldnt get the twrp package to flash so im gonna try with fastboot. But the kernel works, i just swapped the ramdisk from Adam77roots patched kernel with iodak's stock kernel, it should work though
---------- Post added at 07:21 PM ---------- Previous post was at 07:19 PM ----------
Adam77Root said:
Just was about to reply to your PM.
What kind of problem is with the zip package?
I will update the first posts in the afternoon.
Click to expand...
Click to collapse
My twrp failed to flash your twrp.zip package, most likely something on my end though, no one else has reported issues
Hi titan people!
This is my modified kernel with some kernel optimizations and some compiler optimizations.
The goal of abyss is to achieve improved performance/battery without the cost of stability.
I will not be overhauling this project with changes that are not logical to add.
This kernel should work on the latest 7.x.x and maybe 6.x.x roms like CyanogenMod and any other AOSP based rom.
Source links lead to my falcon source because they share the same source
How does one achieve such a compromise?
- build kernel with an optimized toolchain
- use compiler optimization flags (experimental)
- remove redundant code
- improve existing code with more efficient code
- reduce/increase speed of timers (depends on what type of function)
- etc. (most are not easy to explain)
This kernel is built with Linaro GCC 4.9.4 that is optimized for Cortex A7 processors.
Is there actually a performance improvement?
With all the changes added up, there should be. Whether or not one notices the difference is another thing.
Personally, I do feel the performance difference. It is easier to notice the difference with lower level specs like ours.
For those interested in how the kernel optimizations will benefit/work, please look at my github source and read the commit messages.
For those interested in how the compiler optimizations/hacks will benefit/work, please look at this article.
Downloads:
Latest build
BasketBuild
Source:
GitHub
I do not mind if there's some non-development/off-topic discussion here, just no discussion about other works that is nowhere near related to mine.
Also, please refrain from comparing works here; it really kills the spirit of development. Go do that in some other thread.
XDA:DevDB Information
abyss kernel for aosp roms, Kernel for the Moto G 2014
Contributors
YoshiShaPow, arter97, flar2, Christopher83, Cl3Kener, frap129
Source Code: https://github.com/abyss-kernels/falcon
Kernel Special Features:
Version Information
Status: Nightly
Created 2016-05-14
Last Updated 2016-12-09
Main Patches and Features:
- KCAL Control Driver
- kexec hardboot patch for Multirom
- USB Force Fast Charge
- Abyss Optimizations (compiler)
- disabled debugging for more performance throughout
- lots of patches for better performance here and there... too many to list
How to install:
Download kernel from Basketbuild
Boot into TWRP recovery
(If you're coming from a different kernel, dirty flash current ROM)
Flash kernel zip
Reboot
Don't like the defaults?
Use Kernel Adiutor to change the settings!
Frequently Asked Questions:
Is this a custom kernel?
I was asked this question once, and it posed as a real good question. I do not consider abyss kernel to be a "custom kernel" per se, but more so as a modified kernel. The patches and features that go into this kernel do not make it customizable. What they do is improve what has already been implemented. It is like swapping a car's engine for a better one rather than just adding LED flooring lights and fancy car mats.
Can you add [this] and [that] feature?
Something I pride myself with this kernel is that it does not have a bunch of random, useless features or patches mashed into it. Everything put into this kernel is thought out well and tested. I see a lot of works being made popular because it has [this] and [that] feature when really, it's nothing revolutionary. As a matter of fact, most things added to any kernel will not make it 5x better than any other kernel. Most of the time, simple is better; and in this case it definitely is!
First
I'll test
Do you have any preferred settings to tweak the kernel or does it come tweaked out of the box? Thank you.
Ashok Menon 101 said:
Do you have any preferred settings to tweak the kernel or does it come tweaked out of the box? Thank you.
Click to expand...
Click to collapse
Everything is good to go after flashing. The most you could do is increase the Read-ahead size to 258kB or 384kB but there's really no point; it won't do much.
YoshiShaPow said:
Everything is good to go after flashing. The most you could do is increase the Read-ahead size to 258kB or 384kB but there's really no point; it won't do much.
Click to expand...
Click to collapse
Alright, thank you.
Which ROM do you think is the best for this btw? No offence to anyone. I understand that egg-caf goes with everything but which do you prefer? Thank you.
Ashok Menon 101 said:
Alright, thank you.
Which ROM do you think is the best for this btw? No offence to anyone. I understand that egg-caf goes with everything but which do you prefer? Thank you.
Click to expand...
Click to collapse
My current setup is Exodus 6.0 and egg-caf kernel. Sometimes I forget that I'm using a phone (Moto G 2013) that costs less than $200 USD.
New build with modified values; it should improve multitasking performance.
egg-caf-titan-nightly-20160515.zip
YoshiShaPow said:
..... I do not mind if there's some non-development/off-topic discussion here, just no discussion about other works that is nowhere near related to mine.
Also, please refrain from comparing works here; it really kills the spirit of development. Go do that in some other thread. ......
Click to expand...
Click to collapse
As you kindly allow some non-development/off-topic discussion I´d like to ask a question about kernel flashing.
You write in your installing explanation
Boot into TWRP recovery
(If you're coming from a different kernel, dirty flash current ROM)
It´s a thing I often heard before. As an example: When I´m coming from a different kernel (I flashed a custom rom and then changed the kernel) and want to go back to the "stock" one why isn´t it enough to unzip my custom rom and flash the boot.img inside?
Where is the difference to dirty flash the whole rom?
Thx in advance.
Wolfcity said:
As you kindly allow some non-development/off-topic discussion I´d like to ask a question about kernel flashing.
You write in your installing explanation
Boot into TWRP recovery
(If you're coming from a different kernel, dirty flash current ROM)
It´s a thing I often heard before. As an example: When I´m coming from a different kernel (I flashed a custom rom and then changed the kernel) and want to go back to the "stock" one why isn´t it enough to unzip my custom rom and flash the boot.img inside?
Where is the difference to dirty flash the whole rom?
Thx in advance.
Click to expand...
Click to collapse
Your question is not even close to what I mean when I say off-topic :highfive: (it is on-topic). Some kernel developers add scripts, patches, ramdisk modifications, etc in their zips to tune different types of values. The easiest way to get rid of all of that is by dirty flashing the rom, which replaces the /system partition and ramdisk with fresh ones from the dirty flash.
YoshiShaPow said:
Your question is not even close to what I mean when I say off-topic :highfive: (it is on-topic). Some kernel developers add scripts, patches, ramdisk modifications, etc in their zips to tune different types of values. The easiest way to get rid of all of that is by dirty flashing the rom, which replaces the /system partition and ramdisk with fresh ones from the dirty flash.
Click to expand...
Click to collapse
Thx for your fast reply and good to know that my question was on topic.[emoji6] Some devs are very delicate when someone hijacks their thread.
Your answer declares the other files, that can be found in some flashable zip kernels.
Is there something to pay attention of when dirty flashing the same ROM again? Ok,don't wipe data is a clear thing but I think of unmounting partitions etc to don't mess up.
Sent from my Moto G 2014 using XDA-Developers mobile app
Wolfcity said:
Thx for your fast reply and good to know that my question was on topic.[emoji6] Some devs are very delicate when someone hijacks their thread.
Your answer declares the other files, that can be found in some flashable zip kernels.
Is there something to pay attention of when dirty flashing the same ROM again? Ok,don't wipe data is a clear thing but I think of unmounting partitions etc to don't mess up.
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
The Roms updater script will mount the partitions it needs. Just make sure after flashing that you wipe cache and dalvik/art cache. Most gapps have a backup script that prevent it from being removed during dirty flashes. If your gapps are retained, you know you've done it correctly.
YoshiShaPow said:
The Roms updater script will mount the partitions it needs. Just make sure after flashing that you wipe cache and dalvik/art cache. Most gapps have a backup script that prevent it from being removed during dirty flashes. If your gapps are retained, you know you've done it correctly.
Click to expand...
Click to collapse
If someone (a friend oft mine or my cat, not me!) [emoji41] has deleted this backup script because he thought he doesn't need it anymore I think he has to flash gapps again too?
Thx for making things more clear and reminding me not to delete files flippantly.
Sent from my Moto G 2014 using XDA-Developers mobile app
Wolfcity said:
If someone (a friend oft mine or my cat, not me!) [emoji41] has deleted this backup script because he thought he doesn't need it anymore I think he has to flash gapps again too?
Thx for making things more clear and reminding me not to delete files flippantly.
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes you will need to flash gapps again. Make sure that if you still have the backup script to not reflash gapps because I've had conflicts with that before. Not very fun.
YoshiShaPow said:
New build with modified values; it should improve multitasking performance.
egg-caf-titan-nightly-20160515.zip
Click to expand...
Click to collapse
always good to test the new features! downloading :laugh: :victory:
Answer me a question, why should change decipher kernel for egg-caf kernel?
Sent from my Moto G 2014 using XDA-Developers mobile app
DeluxeMark said:
Answer me a question, why should change decipher kernel for egg-caf kernel?
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
Well you should choose:
Decipher: stable,enough features, battery.
Egg: Stable, no extra features, performance.
Performance is much better with egg than decipher.
But in terms of battery, decipher is the clear winner.
I've been using the egg kernel for a few days now with cm13 and it's good enough for me.
Performance is really good. I don't really care about the battery as I always have a charger with me always so I don't really mind.
Overall, egg kernel is pretty good.
DeluxeMark said:
Answer me a question, why should change decipher kernel for egg-caf kernel?
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
How about you answer me this.
OP said:
Also, please refrain from comparing works here; it really kills the spirit of development. Go do that in some other thread.
Click to expand...
Click to collapse
How does one get people to not do something in a thread? Back in the older days, that would be by writing something boldly in the OP. Guess that does not work anymore.
Honestly, you can do whatever the heck you want anywhere else, just not in my thread where I have my posting guidelines set.
Edit: also, I clearly state what is different in my kernel from others in the OP
It was just a question,not a comparison
Sent from my Moto G 2014 using XDA-Developers mobile app
hi all
for those impatient and dare to try, plus able to handle problems ON YOUR OWN as i cannot offer any help at this point:
anyone interested to test an updated version of BeastMode Kernel R154 by @freeza with the latest samsung firmware N960FXXU8FUD1?
please be noted that:
- this might be EXTREMELY DANGEROUS or could BRICK YOUR PHONE in a few seconds, and I am not responsible for bricked devices or any damages which may arise. so, you have been WARNED
- I have NOT TESTED on my n960f yet (just updated to TH4 from pie but not rooted yet for some reasons). SO THINK TWICE!!
- chances the phone may not boot up properly (boot loop or hang) due to the toolchains used to compile the kernel. I have encoutered this before with only one of the four or five gcc i had which booted up the phone successfully
ideal situation to minimize uncertainties:
- already on ud1
- data/cache partition is ext4 formatted (ideally NOT f2fs as supported by bm kernel)
- capable of diagnostic/identify the problems by examining the logcat/last_kmsg and the like would defintely a plus
to be continued...
Hello, Is this gonna work on newer BL version? FUE5 version, also @CyderXDA would wanna try it, but he's on newer BL. We also have Exynos9810 Telegram Chat, there's N9/S9/S9+ users in there that maybe could test for you and stuff if you're interested
JC1126 said:
Hello, Is this gonna work on newer BL version? FUE5 version, also @CyderXDA would wanna try it, but he's on newer BL. We also have Exynos9810 Telegram Chat, there's N9/S9/S9+ users in there that maybe could test for you and stuff if you're interested
Click to expand...
Click to collapse
hi
samsung has just posted a newer firmware N960FXXS8FUE5, probably hours ago, i am going to update it first. will let you guys know
thanks for your interests
ykkfive said:
hi
samsung has just posted a newer firmware N960FXXS8FUE5, probably hours ago, i am going to update it first. will let you guys know
thanks for your interests
Click to expand...
Click to collapse
Alright Goodluck!
JC1126 said:
Alright Goodluck!
Click to expand...
Click to collapse
update 20160616
updated to samsung ue5 sources
i have built 2 different versions, one with gcc 4.9 and the other with gcc 12. there will be only one version in the future (either gcc4 or 12). the reason i built 2 versions this time is in case one of the gcc used doesnt boot probably there's another one to try
differences between @freeza 's R154:
- kernel sources updated (N960F) without any fix or new feature
- not pre-rooted/pre-patched by magisk since the magisk version may differs from what u r using
- NOTE: other devices preiously supported are not recommeded yet, although you may try, i cant make any promise it will work since i didnt look at other devices sources
thinking if i should release it for testing now or wait until i have time to test it myself coz i don want to brick anyone's phone, including mine of coz
ykkfive said:
update 20160616
updated to samsung ue5 sources
i have built 2 different versions, one with gcc 4.9 and the other with gcc 12. there will be only one version in the future (either gcc4 or 12). the reason i built 2 versions this time is in case one of the gcc used doesnt boot probably there's another one to try
differences between @freeza 's R154:
- kernel sources updated without any fix or new feature
- not pre-rooted/pre-patched by magisk since the magisk version may differs from what u r using
- f2fs supported as R154 (cache/data)
thinking if i should release it for testing now or wait until i have time to test it myself coz i don want to brick anyone's phone, including mine of coz
Click to expand...
Click to collapse
Holy that's insane, you added f2fs that's exciting, wonder if it supports AOSP because most of n9 users use aosp, some use noblerom
JC1126 said:
Holy that's insane, you added f2fs that's exciting, wonder if it supports AOSP because most of n9 users use aosp, some use noblerom
Click to expand...
Click to collapse
i didnt add anything new, but i found in his fstab, f2fs is ready. i didnt examine the kernel sources yet. this it true for aosp etc also
so in case f2fs/aosp etc was supported in his R154, it should be, i believe...
sorry, but NO f2fs there in his kernel!!
ykkfive said:
i didnt add anything new, but i found in his fstab, f2fs is ready. i didnt examine the kernel sources yet. this it true for aosp etc also
so in case f2fs/aosp etc was supported in his R154, it should be, i believe...
Click to expand...
Click to collapse
that's cool, can't wait to try it out in lineage a11 lol
JC1126 said:
that's cool, can't wait to try it out in lineage a11 lol
Click to expand...
Click to collapse
i just checked the output, there's no f2fs unfortunately but i can add it later after test
ykkfive said:
i just checked the output, there's no f2fs unfortunately
Click to expand...
Click to collapse
that's still fine tbh, not much difference on ext4, good thing is it works on aosp, idk if it'll boot on oneui3.1 because it needs a permissive kernel to boot so yeah
JC1126 said:
that's still fine tbh, not much difference on ext4, good thing is it works on aosp, idk if it'll boot on oneui3.1 because it needs a permissive kernel to boot so yeah
Click to expand...
Click to collapse
tbf i have not built one with both sammy and aosp supported kernel, and i even don't know his kernel supports aosp
for the one ui 3.1 thing, u mean the ported one? i believe he's made it to run on existing kernel so it should be fine. of coz it needs to be tested first
ykkfive said:
tbf i have not built one with both sammy and aosp supported kernel, and i even don't know his kernel supports aosp
for the one ui 3.1 thing, u mean the ported one? i believe he's made it to run on existing kernel so it should be fine. of coz it needs to be tested first
Click to expand...
Click to collapse
Ohh alright then
update 20210618
the ue5 kernel works properly so far, tested on stock rom only due to unable to get a ue5 custom rom atm
will be released soon
thanks a lot
released, closed
Hello! I've got A6 some time ago, and now trying to mess with XPosed, Magisk, and Root. Everything is cool, except of SELinux, I couldn't switch it to Permissive mode, but I really want to. I had some research recently and it seems like stock Samsung kernels have ALWAYS_ENFORCE function or something. I've already tried to flash a few custom kernels, but (almost?) all of them been made for Android Pie. Unfortunately, I have Android Q.
Do there any way to switch SELinux to permissive besides compiling my own kernel based on Samsung open source? Maybe, I have missed something? It doesn't look's like people have many problems with it...
Thanks in advance!
Just flash some A600X permissive custom kernel, for example Simple Kernel or H-Kernel:
Releases · samsungexynos7870/android_kernel_samsung_exynos7870
Contribute to samsungexynos7870/android_kernel_samsung_exynos7870 development by creating an account on GitHub.
github.com
You can also flash Ares Kernel (it's also permissive).
nqnxev said:
Just flash some A600X permissive custom kernel, for example Simple Kernel or H-Kernel:
Releases · samsungexynos7870/android_kernel_samsung_exynos7870
Contribute to samsungexynos7870/android_kernel_samsung_exynos7870 development by creating an account on GitHub.
github.com
You can also flash Ares Kernel (it's also permissive).
Click to expand...
Click to collapse
Thank you for your reply! I couldn't find Ares Kernel. H-Kernel works for me, but there is a problem — when I flashed Magisk and tried to boot, Samsung logo just didn't appear, and I have stuck on a black screen. Same with a Simple Kernel. Never faced that issue on a stock. Any ideas how to fix this maybe?..
I'll try to search for more kernels, thanks for the tip anyway!
Ares kernel is available here and here (older releases; Ares Iron 6.0 was very stable on my device).
I don't know why Magisk makes troubles during boot on your device.
nqnxev said:
Ares kernel is available here and here (older releases; Ares Iron 6.0 was very stable on my device).
I don't know why Magisk makes troubles during boot on your device.
Click to expand...
Click to collapse
Okay, so I have tried Ares kernel, thanks a lot for the links. Unfortunately, there are same problem with Magisk, so it seems like this is not a specific kernel causing it. To be honest, I don't have any ideas why is this happening too...
I want to install LOLZ Kernel v17 on crDroid 7.13 or 7.12 but I was curious would I lose data if I flag the kernel like do I need to do a full clean install
cause from the instructions I see it only flashes system and vendor
anyone here ever used that kernel with crDroid 7.12 and 7.13?
nope, installing kernels isnt required to do that. if youre still on crdroid, extract your boot and dtbo, thats your default kernel. on here, only lolz is released, but there are a fea other kernels for our devices
fonzacus said:
nope, installing kernels isnt required to do that. if youre still on crdroid, extract your boot and dtbo, thats your default kernel. on here, only lolz is released, but there are a fea other kernels for our devices
Click to expand...
Click to collapse
Have you tried LOLZ Kernel? what do you think about it? or even if you recommend other ones
yep, im currently on havoc 4.14 and lolz 17. the default kernel was buggy, lots of noticeable issues. then i switched over to another kernel not available here and saw some improvements. lolz was a bit better, but id guess its the best kernel for olives.
i havent tried havoc 4.15 yet as it requires a full clean install, but i guess im lazy atm, there are lots of unannounced roms for our phones, pm me and ill give you a tg group to join and look at all the builders ;P
POQDavid said:
I want to install LOLZ Kernel v17 on crDroid 7.13 or 7.12 but I was curious would I lose data if I flag the kernel like do I need to do a full clean install
cause from the instructions I see it only flashes system and vendor
anyone here ever used that kernel with crDroid 7.12 and 7.13?
Click to expand...
Click to collapse
All instructions is on telegram @lolzkenel