Database Develop

[MOD][14 AUG] MultiROM v12

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

[REQ] Lollipop Kernel

Can someone create a modified kernel for Cyanogenmod12 24.11.2014 build, or make Williams kernel working for the same rom? Something with the same fuctions as Williams Kernel (oc,fauxsound and so on). Thanks in advance.

fantamadnesss said:
Can someone create a modified kernel for Cyanogenmod12 24.11.2014 build, or make Williams kernel working for the same rom? Something with the same fuctions as Williams Kernel (oc,fauxsound and so on). Thanks in advance.
Click to expand...
Click to collapse
Can someone also produce a fully working non crashing lollipop build by next tuesday please.
/sarcasm off
Asking for something like this is quite cheeky really, if someone like pecora is working on a lollipop kernel then they will but it takes a lot of work and effort to make something like a kernel. Learn how to code it yourself or just keep en eye on the development folder or better yet ask in pecoras thread if they will be updating for cm12 at all.

Oblox said:
Can someone also produce a fully working non crashing lollipop build by next tuesday please.
/sarcasm off
Asking for something like this is quite cheeky really, if someone like pecora is working on a lollipop kernel then they will but it takes a lot of work and effort to make something like a kernel. Learn how to code it yourself or just keep en eye on the development folder or better yet ask in pecoras thread if they will be updating for cm12 at all.
Click to expand...
Click to collapse
lol, i know its hard but i thought that is not so complicated, since williams kernel v8 is based on 12.1.A.1.207 sources, and so is cm12... So maybe "porting" williams kernel v8 kernel to cm12 is not so complicated? Maybe im wrong, explain me better
EDIT: Mr Steve did it again! By following these instructions Williams Kernel v8 will work on cm12 24.11.2014 build
MrSteve555 said:
Actually the bootloops on Williams kernel started when I added the kernel modules loading on boot in the ramdisk. It could clash with the inbuilt governors and other stuff, so kernel panics could occur.
I think that maybe removing these from the ROM zip could help:
/system/lib/modules/symsearch.ko
/system/lib/modules/cpufreq_limit.ko
/system/lib/modules/cpufreq_abyssplug.ko
/system/lib/modules/cpufreq_adaptive.ko
/system/lib/modules/cpufreq_badass.ko
/system/lib/modules/cpufreq_conservative.ko
/system/lib/modules/cpufreq_intelliactive.ko
/system/lib/modules/cpufreq_intellidemand2.ko
/system/lib/modules/cpufreq_intellimm.ko
/system/lib/modules/cpufreq_lagfree.ko
/system/lib/modules/cpufreq_lionheart.ko
/system/lib/modules/cpufreq_powersave.ko
/system/lib/modules/cpufreq_smartass2.ko
/system/lib/modules/cpufreq_wheatley.ko
/system/lib/modules/bfq-iosched.ko
/system/lib/modules/fifo-iosched.ko
/system/lib/modules/fiops-iosched.ko
/system/lib/modules/row-iosched.ko
/system/lib/modules/sio-iosched.ko
/system/lib/modules/vr-iosched.ko
/system/lib/modules/zen-iosched.ko
/system/lib/modules/zsmalloc.ko
/system/lib/modules/lzo.ko
/system/lib/modules/zram.ko
/system/lib/modules/tcp_bic.ko
/system/lib/modules/tcp_highspeed.ko
/system/lib/modules/tcp_htcp.ko
/system/lib/modules/tcp_hybla.ko
/system/lib/modules/tcp_illinois.ko
/system/lib/modules/tcp_lp.ko
/system/lib/modules/tcp_scalable.ko
/system/lib/modules/tcp_vegas.ko
/system/lib/modules/tcp_veno.ko
/system/lib/modules/tcp_westwood.ko
/system/lib/modules/tcp_yeah.ko
It's the full list, maybe some of them are missing in CM12 package which is not supposed to be used as a daily driver anyway. In the CM11 the files ought to be removed also from 12.5 delta patch. It has a big chance to work
But if it doesn't, well, I can't do much :/
Click to expand...
Click to collapse

Krieg Kernel [03/09/2021] [AOSP]

Just the kernel I use in my Evox builds that everyone seems to enjoy and get really good battery life.
Not much to this op. A Magisk patched boot.img or an unpatched boot.img.
CUSTOM ROMS ONLY!!!
This is patched for Magisk 21.4. Theres a reason behind it, feel free to update as you see fit.
Kernel source: https://github.com/APOPHIS9283/Krieg_Kernel
Patched Boot.img = https://sourceforge.net/projects/un...P8-PRO_Patched_Boot/patched_boot.img/download
Unpatched Boot.img = https://sourceforge.net/projects/un...files/EVOX/OP8_OP8-PRO_Boot/boot.img/download
No flashy OP, No gimmicks just a kernel that seems to work very well for people.
I do not care about ROMs inlining it, please just redirect them here for issues

I updated the kernel it will be available soon

Does support continue for kernel, can you release test and final builds. Will be really nice if it can be done. Currently using Krieg beta.

Will development still be supported? It seems this thread has been reopened and all the replies are cleaned.

Does it work on 8t?

[Closed] BeastMode Kernel update UE5 RELEASED

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

General Info for Redmi Note 11 and kernel source.

Keep in mind, this is not the official source, it has no Xiaomi changes, but it might be helpful for someone.​
The Redmi Note 11 has the SM6225 SoC, codename khaje.
The reason why we didn't get the kernel source is because our phone is GKI compatible, which means the kernel source has been clean and out since the beginning.
Khaje-idp is the dts you should use as base for this phone, as the original dtb is based on the same.
Devicetree for khaje is here
GKI kernel source
Config for building the kernel can be taken from arch/arm64/configs/vendor/bengal-perf_defconfig , or from doing adb pull /proc/config.gz on your own phone, then extracting the file from inside.

Bengal runs 4.19. I don't see how its GKI considering 4.19 has the barebones gki implementation and 5.4 was the first actual gki implementation

cyberknight777 said:
Bengal runs 4.19. I don't see how its GKI considering 4.19 has the barebones gki implementation and 5.4 was the first actual gki implementation
Click to expand...
Click to collapse
5.4 was the first one, but it seems other versions got backported too, can't tell much other than that

sonic011gamer said:
5.4 was the first one, but it seems other versions got backported too, can't tell much other than that
Click to expand...
Click to collapse
That's an IoT tag dude.

cyberknight777 said:
That's an IoT tag dude.
Click to expand...
Click to collapse
My bad then

sonic011gamer said:
Keep in mind, this is not the official source, it has no Xiaomi changes, but it might be helpful for someone.​
The Redmi Note 11 has the SM6225 SoC, codename khaje.
The reason why we didn't get the kernel source is because our phone is GKI compatible, which means the kernel source has been clean and out since the beginning.
Khaje-idp is the dts you should use as base for this phone, as the original dtb is based on the same.
Devicetree for khaje is here
GKI kernel source
Config for building the kernel can be taken from arch/arm64/configs/vendor/bengal-perf_defconfig , or from doing adb pull /proc/config.gz on your own phone, then extracting the file from inside.
Click to expand...
Click to collapse
i dont think gki compatible , since the kernel is still 4.19

Guan Yu said:
i dont think gki compatible , since the kernel is still 4.19
Click to expand...
Click to collapse
It definitely is GKI, the phone has the GKI layout too (even if it's 4.19), check it yourself with parted inside twrp (check every UFS lun)

Are ROM developers aware of this?

I'm working on it, but Im pretty sure it's not GKI. The layout is not saying anything as it is mandatory from android 11 and onwards I think. If you look at the kernel sources from Xiaomi for other devices (Lime for example) you will see that they aren't GKI either. All the drivers are inside the kernel source.
But without schematics and UART connection its pretty much impossible to get it booting (i did try finding uart by luck but dended up destroying my wifi/gps signal), but I am trying. Im kind of confused as of where the DTB lives because we only have a DTBO (overlay) partition and no DTB partition. Its also not appended to the kernel I think but Ill have to check again to be sure.

I found the dtb partition in vendor_boot partition.