Related
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here -
http://forum.xda-developers.com/showthread.php?p=33291894
He'll probably help us out if we make some progress in booting up Codename with it at least
TheDareDevil said:
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here - http://forum.xda-developers.com/showthread.php?t=1899335&page=38
He'll probably help us out if we make some progress in booting up Codename with it at least
Click to expand...
Click to collapse
Upon the exit of JB roms ago, were used GB modified kernel, now with source code maybe will be possible to compile a fully working kernel, but afaik there are no 3.x kernel for JB, maybe someone is working out of xda on irc channel but don't known..
Sadly I do not have much competence, plus I don't have the phone it's to repair....
There is kernel 3 for incredible 2 and desire s..may be someone can port it..
Sent from my HTC Incredible S using xda app-developers app
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
TheMegosh said:
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Well tbh honest a working GB kernel would do too.
Like the front camera and chrome and screen flickering etc.
Damn I wish kaijura was here
Sent from my HTC Incredible S using xda app-developers app
CyanideJack said:
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Click to expand...
Click to collapse
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
ZaySk said:
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
Click to expand...
Click to collapse
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
CyanideJack said:
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
Click to expand...
Click to collapse
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
l0st.prophet said:
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
Click to expand...
Click to collapse
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
ZaySk said:
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
Click to expand...
Click to collapse
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
markj338 said:
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
Click to expand...
Click to collapse
I know, it would be going down a pretty redundant path. If I was able to port over a JB ROM using nik's ROM's as a base, then my ported ROM would inherit all the same bugs nik's ROM's already have.
I wish kaijura was still around, I have so many questions I want to ask about compiling from source! Luckily lordclokan was a massive help to me in that regard. Kaijura's github hasn't seen action in months either, sadly.
Forgive my ignorance, but isn't the Desire HD essentially our device with a bigger screen and less memory? That being the case, could we not just port across one of the 3.0 Kernels from that?
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Well you can prolly get ideas from adi ( he posted http://forum.xda-developers.com/showpost.php?p=33302707&postcount=387 not sure if you saw it) he seems to know what's up.
TheDareDevil said:
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
So it looks like the furthest things got regarding a 3.0 Kernel was;
Adi_Pat said:
chan
Ok so 2.6.35 works with Jellybean. Why not pack the ramdisk with zImage compiled from 3.0.y sources(Considering you are using standard boot.img format[?]) Because to get it to boot, you would not require any hacks/changes to source, editing ramdisk(init.rc) is enough to make it boot initally.
EDIT: You may also need to change init binary.
Click to expand...
Click to collapse
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Very interesting, thanks for the informative post. :good:
zaysk said:
very interesting, thanks for the informative post. :good:
Click to expand...
Click to collapse
happy november!!!
markj338 said:
happy november!!!
Click to expand...
Click to collapse
A very happy November indeed
Guys,
I have found below link.
Can any of our kernel developers(non verbose, prophet10) confirm if this can be used for code 3.5.0 Nik JB ROM?
It says universal kernel for all JB and AOSP ROMs....
http://forum.xda-developers.com/showthread.php?t=1862557
You won't be able to flash it.
Its not for our device.
Offtopic: Everytime when somebody is asking about an AOSP Kernel for ICS/JB i just think. Shut the **** up.
If there is someday an AOSP Kernel for ICS/JB for our Device, wou'll find it @ Dev Section for Incredible S and not somewhere different.
Silversniper said:
You won't be able to flash it.
Its not for our device.
Offtopic: Everytime when somebody is asking about an AOSP Kernel for ICS/JB i just think. Shut the **** up.
If there is someday an AOSP Kernel for ICS/JB for our Device, wou'll find it @ Dev Section for Incredible S and not somewhere different.
Click to expand...
Click to collapse
did you try it before?
@di said:
Guys,
I have found below link.
Can any of our kernel developers(non verbose, prophet10) confirm if this can be used for code 3.5.0 Nik JB ROM?
It says universal kernel for all JB and AOSP ROMs....
http://forum.xda-developers.com/showthread.php?t=1862557
Click to expand...
Click to collapse
I've taken a look at the original thread, but where have you seen that is a universal kernel? For me it says that works with every aosp rom for THAT phone, not on ANY phone....
bob8x said:
I've taken a look at the original thread, but where have you seen that is a universal kernel? For me it says that works with every aosp rom for THAT phone, not on ANY phone....
Click to expand...
Click to collapse
look at the first line!!!!!!
"Current kernel features include: (If feature begins with a * then check below for more information)
Universal kernel compatible with all AOSP (NOT SENSE) ICS & JB roms"
sorry friend if I have missed on anything. I just saw it and thought it might be useful.....
Looked into the updater script, and we would be able to flash it, but anyway, it shouldnt work.
Kernel is the connection between Hardware and software, and their device do have another hardware...
@di said:
look at the first line!!!!!!
"Current kernel features include: (If feature begins with a * then check below for more information)
Universal kernel compatible with all AOSP (NOT SENSE) ICS & JB roms"
sorry friend if I have missed on anything. I just saw it and thought it might be useful.....
Click to expand...
Click to collapse
Well I read that line too, I meant "where have you seen that is a universal kernel" for every phone? .
Again I assume that universal stand for "for every rom designed for this phone": take in example redux kernel, it has 3 version: sabsa,virtuos, projectX ; that kernel will work for every rom without fix or specific version...
bob8x said:
Well I read that line too, I meant "where have you seen that is a universal kernel" for every phone? .
Again I assume that universal stand for "for every rom designed for this phone": take in example redux kernel, it has 3 version: sabsa,virtuos, projectX ; that kernel will work for every rom without fix or specific version...
Click to expand...
Click to collapse
hmm, yaaa you may be right Bob
anyways to avoid any confusion, I have PMed that developer copying the same "universal" line, to check if this is flashable with each and every AOSP ROM.....
@di said:
hmm, yaaa you may be right Bob
anyways to avoid any confusion, I have PMed that developer copying the same "universal" line, to check if this is flashable with each and every AOSP ROM.....
Click to expand...
Click to collapse
This Kernel will not work on our IncS. When you try to flash this, its like you're trying to install a nvidia Driver for an AMD GPU. It wont work!!
This is only universal for myTouch 4G, not universal for all devices. If it will run on our IncS, the dev will write this down in the thread and will create a thread in the IncS-Section.
Ok!!!! Guys Sorry for the confusion!!!!!
Sent from my HTC Incredible S using xda app-developers app
I was so excited!
And now I an disappoint: (
Sent from my Incredible S using xda app-developers app
It would mean universal for all mt4g or whatever device
It works on all sense, aosp, miui ROMs for them. Kernels are specific to hardware. Not even dinc2 kernels work for us
Sent from my Nexus 7 using the xda app
Please stay tuned
Reserved
I heard this kernel is one of great kernel in GNex forum.
I'll flash it right away
Sent from my Nexus S using Tapatalk 2
Cool, I love flashing new releases
A new challenger appears! I'll have to try this out sometime in the near future, but it will be hard to tear me away from Marmite.
Sent from my Nexus S using xda app-developers app
Does not boot.
using latest CM10 nightly
Brishen said:
Does not boot.
using latest CM10 nightly
Click to expand...
Click to collapse
No Custom IOCTL stuff I guess..
Sent from my Nexus S using Tapatalk 2
Op does not Specify weather this Kernel is for,
CM Based roms
AOSP Based roms
AOKP Based Roms
I Tried it on Latest Paranoid Android (CM Based) and it black screens.
Is now compatiable with AOSP ROMS Only. I will have bbedward from post #2 look into some of the comments here. He is our kernel developer building blindly on this device
Thank you all for trying and posting your experiences, we will certainly get you fixed up!
Purian23
Thank you for your sharing.
purian23 said:
Should be compatible with all ROMS out there. Same as it is on the Nexus. I will have bbedward from post #2 look into some of the comments here. He is our kernel developer building blindly on this device
Thank you all for trying and posting your experiences, we will certainly get you fixed up!
Purian23
Click to expand...
Click to collapse
AOSP and AOKP based roms use the same Kernels but CM Based roms use different Kernels and will not work unless setup specifically for CM Roms.
This is 5.4 MB? Hmmm...need to see how it performs.
Tested this kernel. Overall snappy & fast with Ondemandx even at stock speeds. There is no bigmem support. This is very important for Nexus S due to low available memory. Screen colors look too yellow. This can be adjusted by user if Voodoo color is included. Inclusion of USB fast charge will give an added advantage.
anshumandash said:
Tested this kernel. Overall snappy & fast with Ondemandx even at stock speeds. There is no bigmem support. This is very important for Nexus S due to low available memory. Screen colors look too yellow. This can be adjusted by user if Voodoo color is included. Inclusion of USB fast charge will give an added advantage.
Click to expand...
Click to collapse
also no Crt Fix ..
Didnt work for me with a cm10.
raducux said:
Didnt work for me with a cm10.
Click to expand...
Click to collapse
will a cm10 version be available?
Its based on aosp source and was tested on crossbones ROM, I'll get the rest of you guys figureld out soon.
---------- Post added at 02:18 PM ---------- Previous post was at 01:22 PM ----------
Big Dog KMc said:
AOSP and AOKP based roms use the same Kernels but CM Based roms use different Kernels and will not work unless setup specifically for CM Roms.
Click to expand...
Click to collapse
I understand, looks like CM requires a kernel patch for this http://review.cyanogenmod.org/#/c/23541/
I was unaware as it was tested on an aosp based rom
We made a decision here, we're not going to support CyanogenMOD officially.
We will update the OP accordingly, it's just not desirable to maintain 2 builds for 1 device. The kernel should be fully compatible with AOSP/AOKP, and will be the kernel bundled with the CrossBones rom.
If you wish to use this kernel on CyanogenMod, you may build a copy yourself using herring_zen_defconfig and setting CONFIG_FOR_CYANOGENMOD=y . Keep in mind unofficial builds won't be officially supported by us. Please when building an unofficial kernel ALWAYS SET CONFIG_ZEN_VERSION_CODE=0. While it may not have any affect now, it may affect some userspace apps.
The kernel source is located here: https://github.com/AndroidDeveloperAlliance/ZenKernel_Crespo
We also provide a custom prebuilt GCC toolchain you can use here: https://github.com/AndroidDeveloperAlliance/ZenKernel_ARCH_armv7a_compiler
Only official builds are supported!
Thanks
bbedward said:
We made a decision here, we're not going to support CyanogenMOD officially.
We will update the OP accordingly, it's just not desirable to maintain 2 builds for 1 device. The kernel should be fully compatible with AOSP/AOKP, and will be the kernel bundled with the CrossBones rom.
If you wish to use this kernel on CyanogenMod, you may build a copy yourself using herring_zen_defconfig and setting CONFIG_FOR_CYANOGENMOD=y . Keep in mind unofficial builds won't be officially supported by us. Please when building an unofficial kernel ALWAYS SET CONFIG_ZEN_VERSION_CODE=0. While it may not have any affect now, it may affect some userspace apps.
The kernel source is located here: https://github.com/AndroidDeveloperAlliance/ZenKernel_Crespo
We also provide a custom prebuilt GCC toolchain you can use here: https://github.com/AndroidDeveloperAlliance/ZenKernel_ARCH_armv7a_compiler
Only official builds are supported!
Thanks
Click to expand...
Click to collapse
Looks like I won't be trying this kernel, then.
Stay tunes for V2, thanks for the feedback from some of you. Added bigmem, voodoo color support, usb fast charge support, some more lowmemorykiller upstream updates, and also cifs+fuse FS support.
ScOULaris said:
Looks like I won't be trying this kernel, then.
Click to expand...
Click to collapse
We're offering this to the community with no expectations that you use it, but for those who do use it we want them to be completely satisfied.
If it doesn't work for you, then I encourage you to use something from one of the other great development teams out there.
I thought of a couple solutions: 1.) creating 2 kernel builds, 2.) creating a sysfs interface so CM users could flash an init script that'd enable the CM ioctl's. Basically it comes down to this - neither solution is up to my standards for now.
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
There is this threads (Tested Roms on SPH-L720T )but unfortunately it seems OP has stopped updating it. So I started this thread trying to keep this topic updated.
Results below are either from my own experience, or from posts by other fellow xdaers.
You are welcome to pm me for new info or corrections. I will try my best to keep this post updated as long as I still own this phone.
Please note, working-non working status or issues should be modem specific. Therefore results from my phone only speak for NG5.
1) ROMs works well:
1.1) Stock NG5, OA3:
1.2) [UNOFFICIAL][5.0.2][CM-12.0] CyanogenMod 12 for jfltespr (2015-01-26 / FINAL: Working
1.3) [LXR22G][5.0.2] Team OctOs Oct-L: Working
1.4) [OFFICIAL] CyanogenMod Nightly Builds for jfltespr
Followings are reported working by others:
1.5) C-Rom 7.1 (#78): some issues where it says digital roaming sometimes. It didn't seem to be as good a connection for LTE as stock rom and it dropped to 3G more often.
1.6) SuperS4 (#80): the newest SuperS4 does have the spark icon.
1.7) BeanStalk ROM (4.4.4): It's completely stable and has just about every possible customization baked right into the ROM including xposed installer.
1.8) SlimKat ROM (4.4.4): keeps the ROM stock,only customize a little, always a rock solid ROM with exceptional support and almost perfect code.
1.9) PacMan ROM (4.4.4)：
1.10) Mahdi ROM (says digital roaming instead of Sprint but works perfectly)
1.11) Negalite WonderRom v3 (4.4.2), working with NG5.
2) Roms Not working so well:
2.1) Sacs_Custom_Rom_V3_NG2_9_24_14 : Wifi not working. ktoonez kernel fixes WiFi but with lag. The issue might be modem specific.
2.2) [ROM] [ jfltespr ][ Feb 10 ] AICP - 8.0 - LP 5.0.2_r1 | OFFICIAL NIGHTLIES: Phone runs warm / battery drain
Update: warm/battery issue seems fixed in 3-1 nightly.
Update2: 3-13 nightly introduced tint. I'm back to 3-3.
2.3) 【5.0.1】Google Play Edition 【JFLTE-GPE】, 2-23-2015 build: Phone runs warm / battery drain
（Below are reported by others）
2.4) Triforce + ktoonez kernel to get the WiFi working: FC from time to time though.
TW Lollipop available for play with:
1) Echoe team tw Lollipop rom v43. I tried it out and data works after some tweak. Unfortunately Echoe team has just quit xda.
2) Albe95's rom.
3) sac23's ported rom from 2).
First Thanks for this....
I'm using Negalite WonderRom v3 with no problems.
It is android 4.4.2 though, and it replaced my TWRP 2.8.4.0 with Philz recovery.
I'm waiting around hoping for a TW Lolipop update.
Edit: I am also on the NG5 modem.
Thanks for this. :good: :good:
I think it might be helpful to post links to the ROMs threads? :angel:
JerryGNYC said:
Thanks for this. :good: :good:
I think it might be helpful to post links to the ROMs threads? :angel:
Click to expand...
Click to collapse
Will do when I get back to my desktop.
Thank you soooooo much for this list! The people in the "all things SPH-L720T" thread MOD EDIT: Disrespect to forum members removed. Please read forum rules!when I asked for a list of compatible ROMs which didn't break any features, with a dev of OctOS being king prick and basically saying that modding/hacking shouldn't be easy for others because it wasn't easy for him.
For anyone who's doing testing for ROMs on this phone, please be aware of HOW to check if GPS is working - this is a commonly broken feature in custom ROMs for this model. It seems that many ROMs will appear to work fine with your initial location, but when you move around the GPS won't track. I suggest using some form of active navigation program to test while you're traveling. Might be useful to append this to the OP.
I have an NG5 720T... TWRP 2.8.4 worked to root for me, had the same issue that 2.8.5 didn't - however, 2.8.4 didn't work for me the first time, either... I suspect that the data transfer is slower than it appears and it's important to let things "settle" for a few minutes before unplugging/rebooting. When I stopped being anxious and trying to rifle through the rooting process as fast as possible (instead, doing it while cooking) it went off without a hitch.
As an aside, I was wondering if we could also get a list of compatible Kernels.
Last but not least, if I install a custom ROM/Kernel on NG5 and then update to OA3 are things going to break? OA3 is important to me because I intend to use FreedomPop as a provider and ALL of their service is data-based (lots of WiFi calling will be done).
shadowcliffs said:
Guys, I just started a new thread specialized in collecting info of various ROMs working or partly/non-working with L720T.
Click to expand...
Click to collapse
Thanks, info from your op has been added to http://forum.xda-developers.com/showthread.php?p=59081315 with credit to shadowcliff.
Please note this quote from my op "This thread/OP (Post 1) is meant to be a centralized summary of all that has been learned about the 720T phone."
I am trying to centralize SPH-720T support as much as possible. Centralizing support is important and good for all of us.
Please understand that Centralization is what has made this thread so helpful to so many, and I would appreciate if you would not try to break this thread apart.
Thanks
bgmg said:
Thanks, info from your op has been added to http://forum.xda-developers.com/showthread.php?p=59081315 with credit to shadowcliff.
Please note this quote from my op "This thread/OP (Post 1) is meant to be a centralized summary of all that has been learned about the 720T phone."
I am trying to centralize SPH-720T support as much as possible. Centralizing support is important and good for all of us.
Please understand that Centralization is what has made this thread so helpful to so many, and I would appreciate if you would not try to break this thread apart.
Click to expand...
Click to collapse
Ignore this please. This thread is FOCUSED on ROM experimentation and if anything bgmg is the one stifling progress with the L720T by trying to mandate that his be the only thread about the phone. It's far more efficient to have specialized threads that are LINKED TO instead of the MOD Edit: DO NOT USE PROFANITY, disguised or filtered intention is clear. Intelligent people can express themselves without it that his thread's OP is becoming.
Keep up the good work, everyone.
BTW, has anyone tested EchoeRom? I hear tell there's a jfltespr version floating around somewhere...
I only find v1 here http://forum.xda-developers.com/showthread.php?t=2521870. Would you like to share the link to v3?
fuzzybuffalo said:
First Thanks for this....
I'm using Negalite WonderRom v3 with no problems.
It is android 4.4.2 though, and it replaced my TWRP 2.8.4.0 with Philz recovery.
I'm waiting around hoping for a TW Lolipop update.
Edit: I am also on the NG5 modem.
Click to expand...
Click to collapse
shadowcliffs said:
I only find v1 here http://forum.xda-developers.com/showthread.php?t=2521870. Would you like to share the link to v3?
Click to expand...
Click to collapse
You have to use his SVN to get version 3.
@shadowcliffs
I'd like to suggest adding links to the development threads of the ROMs listed in the OP.It's easy enough to find them via google or a forum search, but ease-of-access benefits everyone.
Dirty Unicorns 9.1 jflte
confirmed working
When adding a ROM, please post links to the ROM's thread or home page... Thanks.
It seems there is some drama between Echoe team and xda that Echoe team quited xda. Oh well, our lost.
Now I'm looking forward to Able95's tw lollipop rom and sac23/s port.
BTW, for Echoe rom v43: sms/mms not tested for I'm with Freedompop and data is all I care.
To hell with that "spark wheel".
Lol, not a fan
shadowcliffs said:
Why wait for Touchwiz Lollipop from Sprint? It's here!
Just got [EXCLUSIVE!!] UPDATE! 06 MARCH] [I9505XXUHOB7-Android 5.0.1] The Echoe Rom- EchoePop to fully work on my L720T including the Spark wheel! Well almost, I think eri.xml and csc still need some work. For those brave, you can flash the rom in that link and apply apns-conf.xml and build.prop from me, or wait for @sac23 to release his official port. Cheers!:victory:
build.prop
apns-conf.xml
Click to expand...
Click to collapse
Awesome! Thanks for this... will you be updating when @sac23 releases his official port?
shadowcliffs said:
Why wait for Touchwiz Lollipop from Sprint? It's here!
Just got [EXCLUSIVE!!] UPDATE! 06 MARCH] [I9505XXUHOB7-Android 5.0.1] The Echoe Rom- EchoePop to fully work on my L720T including the Spark wheel! Well almost, I think eri.xml and csc still need some work. For those brave, you can flash the rom in that link and apply apns-conf.xml and build.prop from me, or wait for @sac23 to release his official port. Cheers!:victory:
build.prop
apns-conf.xml
Click to expand...
Click to collapse
How in the world were you able to get this to work? I copied my original APNS config when updating, and heavily edited the build.prop file but just couldn't get SMS/MMS working.
EDIT: So since the entire crap storm that is ECHO rom at the moment, I decided to try this on Albe's touchwiz rom, and everything works except sms/mms. You can recieve messages and pics but cannot send anything at all . Had to revert back to GPE
Has anybody had any luck with flashing anything on the OA3 firmware? Everything I have tried including NG5 has broken wifi. I even tried flashing the NON-HLOS.bin. My phone came with OA3.
My ROMs: Wicked X & Wicked S5 Xperience
bilgerryan said:
Has anybody had any luck with flashing anything on the OA3 firmware? Everything I have tried including NG5 has broken wifi. I even tried flashing the NON-HLOS.bin. My phone came with OA3.
My ROMs: Wicked X & Wicked S5 Xperience
Click to expand...
Click to collapse
My phone comes with NG5 and has been updated to OA3.
I have listed roms I tried out in OP. I can say that all cm lollipop roms have working wifi with stock kernel and I haven't seen a tw lollipop rom with working wifi without custom kernel so far.
shadowcliffs said:
My phone comes with NG5 and has been updated to OA3.
I have list roms I tried out in OP. I can say that all cm lollipop roms have working wifi with stock kernel and I haven't seen a tw lollipop rom with working wifi without custom kernel so far.
Click to expand...
Click to collapse
I guess I need to make a flashable for the L720T OA3 kernel. That might solve the problem if you flash it after the ROM.
My ROMs: Wicked X & Wicked S5 Xperience