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
Novastar CM-10.1 UNOFFICIAL nightlies​
I've been compiling nightlies for personal use with my personal preferences included and since I noticed a lot of people run this setup I figured I'd share it, since it's pretty nice not to have to flash three or more zips every update.
This is meant to be an uncomplicated ROM with amazing screen calibration, good performance without having to fiddle with settings for ages and with the best new CM features.
Features:
CM-10.1 UNOFFICIAL NIGHTLY
Cherry picked:
- libstagefright: support for disabling buffer metadata
Harsh kernel [Linux 3.4.39]
- always up to date
- no need for configuration apps, runs great by default
Hardcoded halfbreed screen calibration by molesarecoming
- the best looking screen calibration for the Nexus 4, amazing improvement
- automatically integrated into the kernel ('hardcoded')
Nexus 4 default boot animation
- because I don't like CM-10.1 boot animation and of course we're all proud to be a Nexus owner.
I'm going to try to do daily updates to the ROM and the kernel and I'm open to cherry picks if you request them. Usually I don't add them myself, because not introducing bugs typically outweighs not having to wait for a few extra days. But if you guys have a special request I'll be happy to add it.
Download
Install instructions:
You can flash without wiping anything if you're coming from another CM-10.1 ROM or from a earlier version of this ROM (the CM install script wipes everything required automatically, wiping dalvik and cache isn't necessary). If you're coming from another ROM you probably don't need to wipe, but if you're getting errors try a clean install. Always do a NANDROID backup before installing!
Gapps are - as usual in CM ROMs - not included. You need to flash them the first time you install the ROM and every time you do a factory reset. You can download the most recent gapps here.
About goo.im:
There will be versions showing on the servers that are still being uploaded. If you download files that are significantly smaller than usual you're most likely downloading half of a ROM.
I've also included an automatic upload script to my build procedure. This means that there will be builds appearing on goo.im that are experimental. Usually they'll be fine, but if you want to be sure, only download after the announcement in this thread.
Credits go to:
CyanogenMod
aremcee (as CM device maintainer for our device)
Harsh (for making the best kernel)
molesarecoming (for his amazing efforts on calibrating our screen)
Previous versions
Re: [ROM][CM-10.1][4.2.2][Feb-16] Novastar nightly KANGs [Harsh kernel 4.2.2][Halfbre
Thank you.
Sent from my Nexus 4 using xda premium
Very nice, I think I will give this ROM a try. I assume as with most ROMs GAPPS is not included and needs to be flashed separately?
Chochiwpg said:
Very nice, I think I will give this ROM a try. I assume as with most ROMs GAPPS is not included and needs to be flashed separately?
Click to expand...
Click to collapse
Yes. But they 'stick' when upgrading, so it's not required to flash them after the first time (unless you wipe, of course).
Re: [ROM][CM-10.1][4.2.2][Feb-16] Novastar nightly KANGs [Harsh kernel 4.2.2][Halfbre
Does this work with the new baseband?
Michealtbh said:
Does this work with the new baseband?
Click to expand...
Click to collapse
I haven't tested it yet, but it should, as the kernel source is already synced with the new source.
I'll test later.
Re: [ROM][CM-10.1][4.2.2][Feb-16] Novastar nightly KANGs [Harsh kernel 4.2.2][Halfbre
Michealtbh said:
Does this work with the new baseband?
Click to expand...
Click to collapse
Yes, especially because it's a 4.2.2 ROM.
Sent from my Nexus 4 using xda premium
New version
CM 10.1 updated until: Ic8a6b748
Harsh kernel: no changes
Cherry picked: I96c4ac11 - PowerUsage: show more apps in battery statistics
DOWNLOAD
Sounds interesting, I'll give it a try!
thank you. I will try this tomorrow
Hey flashed your ROM, it's running smooth and stable, but I am used to AOKP in terms of customization.
Too much missing for my taste. But I think this ROM isn't meant to be so customizable.
I like the hardcoded harsh kernel, because normally the harsh kernel comes with stock colors and has to be modified.
laba86 said:
Hey flashed your ROM, it's running smooth and stable, but I am used to AOKP in terms of customization.
Too much missing for my taste. But I think this ROM isn't meant to be so customizable.
I like the hardcoded harsh kernel, because normally the harsh kernel comes with stock colors and has to be modified.
Click to expand...
Click to collapse
Yea, this is just stock CM 10.1.
A Harsh kernel with hardcoded gamma settings that could run on any ROM (including AOKP) is on my to do
I don't mean to sound disrespectful, but shouldn't this be in 'Android Development?' Since this is a kang, it's not classified as 'original,' unless I'm wrong...
Notorious544d said:
I don't mean to sound disrespectful, but shouldn't this be in 'Android Development?' Since this is a kang, it's not classified as 'original,' unless I'm wrong...
Click to expand...
Click to collapse
Requested the thread to be moved. I never really understood the difference between the different dev sections, but you're probably right since this ROM is not original, just parts of other developers combined.
Nova163 said:
Requested the thread to be moved. I never really understood the difference between the different dev sections, but you're probably right since this ROM is not original, just parts of other developers combined.
Click to expand...
Click to collapse
Android Development: Kangs, cooked, etc.
Original Development: Stuff like CM, AOKP, SlimBean, XenonHD, most kernels, etc.
New version
CM 10.1 updated until: If6c2ab39
Harsh kernel: no changes
Cherry picked:
framework: Battery bar (1/2)
Settings: Battery bar (2/2)
Calculator: New Features Part 3
settings.cyanogenmod: Added option to always pull down quick settings
DOWNLOAD
Added a few new cherry picks I like.
Found a bug in the incall screen the phone goes blank thought it was my case but no its not otherwise everything is awesome and speedy with great battery life
Re: [ROM][CM-10.1][4.2.2][Feb-16] Novastar nightly KANGs [Harsh kernel 4.2.2][Halfbre
Running beautifully and the colors looks amazing also. Loving it lol, just give me a center clock and I'll be in heaven lol
Sent from my Nexus 4 using xda premium
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
saniyal said:
Found a bug in the incall screen the phone goes blank thought it was my case but no its not otherwise everything is awesome and speedy with great battery life
Click to expand...
Click to collapse
Is working fine here.
Sent from my Nexus 4 using xda premium
Re: [ROM][CM-10.1][4.2.2][Feb-16] Novastar nightly KANGs [Harsh kernel 4.2.2][Halfbre
Rotation is a no go tho. Sensors are out.
Sent from my Nexus 4 using xda premium
A member from tinhte.vn (a Vietnamese smartphone website) built a version of Kowalski kernel specifically for SU660.
Pls come to this site: http://www.tinhte.vn/threads/lg-opt...p-rom-root-fix-loi-update-ics-cm10-1.1292092/ - (I think this the best site ever for SU660)
and search for: minhhang129
or you can download here http://www.mediafire.com/?qlrkn9a2yjbiu7p
BIG THANKS TO MINHHANG129 FROM VIETNAM
"Words from Minhhang129 to pengus77: thank you - you are of great help to SU660 community"
This file should be flashed after you flash standard official cm10.1 nightly (which you have to remove the P990 assert as aragorn7's guide here: http://forum.xda-developers.com/showthread.php?t=1850967).
The kernel works fine - just remember to come to setting/performance/processor and change minimum cpu freq to 216
WARNING: YOUR PHONE MAY BRICK - YOU HAVE BEEN WARNED
Re: Kowalsky kernel for SU660 - for CM10.1 Nightly
su660ics said:
A member from tinhte.vn (a Vietnamese smartphone website) built a version of Kowalsky kernel specifically for SU660.
Pls come to this site: http://www.tinhte.vn/threads/lg-opt...p-rom-root-fix-loi-update-ics-cm10-1.1292092/ - (I think the this the best site ever for SU660)
and search for: minhhang129
or you can download here http://www.mediafire.com/?qlrkn9a2yjbiu7p
BIG THANKS TO MINHHANG129 FROM VIETNAM
This file should be flashed after you flash standard official cm10.1 nightly (which you have to remove the P990 assert as aragorn7's guide here: http://forum.xda-developers.com/showthread.php?t=1850967).
The kernel works fine - just remember to come to setting/performance/processor and change minimum cpu freq to 216
WARNING: YOUR PHONE MAY BRICK - YOU HAVE BEEN WARNED
Click to expand...
Click to collapse
thanks man will try this soon.
what build of kowalsky?
Sent from my LG-P990 using xda premium
Uhm, really ? Would be nice to have had a heads up at least before building this... i'm actively developing this kernel and i don't find it really fair to just pick it up and compile it as-is.
BTW it's kowalski, not kowalsky...
Tell the guy who ported it to the SU660 to send me pull requests on github with his fixes please, so i can build SU660 versions directly from my source and keep it in sync with the P990 one
pengus77 said:
Uhm, really ? Would be nice to have had a heads up at least before building this... i'm actively developing this kernel and i don't find it really fair to just pick it up and compile it as-is.
BTW it's kowalski, not kowalsky...
Tell the guy who ported it to the SU660 to send me pull requests on github with his fixes please, so i can build SU660 versions directly from my source and keep it in sync with the P990 one
Click to expand...
Click to collapse
Hi pengus77, sorry if you feel it inconvenient. This guy minhhang129 only compiled a version - which serves as temp because since CM team upgrade to CM10.1 , the wkpark kernel seemed not work anymore.
This guy's english is no as good, and so is mine. And I actually am a casual user who dont know about technical matters, things about github and fixes prove too much for me - thats why this version only works like a waiting version for SU660 user who really want a working kernel (though with some acceptable bugs) for old bootloader CM10.1 Nightly and only so
We are looking forward to hearing from your kernel for SU660 and thank you.
P/S: I have changed the name
su660ics said:
Hi pengus77, sorry if you feel it inconvenient. This guy minhhang129 only compiled a version - which serves as temp because since CM team upgrade to CM10.1 , the wkpark kernel seemed not work anymore.
This guy's english is no as good, and so is mine. And I actually am a casual user who dont know about technical matters, things about github and fixes prove too much for me - thats why this version only works like a waiting version for SU660 user who really want a working kernel (though with some acceptable bugs) for old bootloader CM10.1 Nightly and only so
We are looking forward to hearing from your kernel for SU660 and thank you.
P/S: I have changed the name
Click to expand...
Click to collapse
First, unless someone can get that guy 'minhhang129' to work with Pengus77, we won't be enjoying this kernel's full feature (it comes with OC but not really working)
Second, why is it only for CM10.1? :/
I'm not really fond of using that ROM so I think I will just stick to using PA + wkpark's kernel
last, just want to thank Pengus77 for his concern and I blame TS for the misspelled Kowalski hahah
Sent from my LG-SU660 using xda premium
genemini said:
First, unless someone can get that guy 'minhhang129' to work with Pengus77, we won't be enjoying this kernel's full feature (it comes with OC but not really working)
Second, why is it only for CM10.1? :/
I'm not really fond of using that ROM so I think I will just stick to using PA + wkpark's kernel
last, just want to thank Pengus77 for his concern and I blame TS for the misspelled Kowalski hahah
Sent from my LG-SU660 using xda premium
Click to expand...
Click to collapse
, I dont really compile it out this kowalski kernel so dont blame me hehe minhhang must know this but me dont
This kernel allow OC actually, I am using max processor freq at 1200 which you can max it at 1456. It's a pity but as I said minhhang's english is not so good and I only know him online so cant work out. Can I ask you one thing: is paranoid good??? I really want to try it , hehe, but does everything work right now? eg. video decoder etc
Trying the PA 2.5. it boots forever
Can you show me how to install PA, it seems goods
yup, it's very smoooooth!
I'm currently on build4 and never had issue, video playback is fine too(I'm using MX Player), games are all working well too.
I actually tried build5 but some apps and games are not working for me so i revert back to build4
its worth a try! heheh
genemini said:
yup, it's very smoooooth!
I'm currently on build4 and never had issue, video playback is fine too(I'm using MX Player), games are all working well too.
I actually tried build5 but some apps and games are not working for me so i revert back to build4
its worth a try! heheh
Click to expand...
Click to collapse
I've just tried it and see a lot of potential in there, especially the nav - bar. Very cool. But version 2.3 is without project butter I think. I am using CM10.1 for long and when use 2.3 version I still see version 2.3 not as smooth as cm10.1 nightly. Maybe just my feeling. I just back off to CM10.1
If pengus77 can build a version of his famous kernel for SU660 which can run PA 2.6 - I think I will stick with this Paranoid Android - It's very cool
Tks anyway and pray for a new kernel for PA 2.6
you can use wkpark's fix and kernel for PA 2.6 too.
just download PA ROM 2.6 (whichever build u like) then rename it to 'cm-10-20130106-NIGHTLY-p990'
someone can make a kernel for the new bootloader??
genemini said:
you can use wkpark's fix and kernel for PA 2.6 too.
just download PA ROM 2.6 (whichever build u like) then rename it to 'cm-10-20130106-NIGHTLY-p990'
Click to expand...
Click to collapse
Thanks it works great. No call bug till now, no bsod - great rom
Kowalsky kernel for SU660 with new bootloader any one have..??
deleted
reported it to be deleted.
wait till tomorrow for my new personal build
Will complete it later on.
Will complete it later on.
wuut?
This is yours CM7 or based on CM7 bieltv?
Alucard1989pl said:
This is yours CM7 or based on CM7 bieltv?
Click to expand...
Click to collapse
Yep my cm7 built from source
The device trees are by biel which I am working on.
downloading .... report in half an hour ...!
EDIT: Sbrick too, trying with hell lock now...
Phone has soft brick by kernel in your cm7 rom . . . system data and cache must be formated to ext4?
Alucard1989pl said:
Phone has soft brick by kernel in your cm7 rom . . . system data and cache must be formated to ext4?
Click to expand...
Click to collapse
use hells fusion from the other thread..
I already use hells fusion kernel but when i installed your cm7 my phone stuck on splash screen and led for 1 sec turn on.
Alucard1989pl said:
I already use hells fusion kernel but when i installed your cm7 my phone stuck on splash screen and led for 1 sec turn on.
Click to expand...
Click to collapse
logcat? its really weird cuz it worked for someone else..
what instructions did u use?
prototype-U said:
use hells fusion from the other thread..
Click to expand...
Click to collapse
Please include your kernel in this thread to make it clearer
You have to use this updater-script for flash cm7. If you don't use this one, the phone will get bricked. http://pastebin.com/htJ8NYTs
For use this updater-script you have to put in the first root of the zip two files: bmlunlock and busybox.
Remember to add the boot.img of hells fusion kernel at second post!
P.S. OP I think that you have to give credits to biel!
Soft Brick. Tried with hell lock flashable zip, softbrick with flashlight with 2 seconds. Now tried with the kernel you provided, stuck on the SGAi bootlogo. Any solution? You said it worked on someone else's device... How did he install? From stock or another rom?
EDIT: Now will try with the updater script you said, @Lopicl.00 . What attachment are you talking about?
mathm2013 said:
Soft Brick. Tried with hell lock flashable zip, softbrick with flashlight with 2 seconds. Now tried with the kernel you provided, stuck on the SGAi bootlogo. Any solution? You said it worked on someone else's device... How did he install? From stock or another rom?
Click to expand...
Click to collapse
Follow my post!
bricked the device while trying to install this rom, i had the kernel from your threat
Angryace said:
bricked the device while trying to install this rom, i had the kernel from your threat
Click to expand...
Click to collapse
Threat is something that puts you in danger
Well, I don't know which is the point of this thread. You are building my sources. You are making my ROM. Why create another thread? You don't have the device, me neither, but I started that project from 0. Why instead of making your CM7 you don't help us? Why don't you make a pull request? Do we need to talk with testers, which are the same for the both of us, to just test the same ROM!? If we want to have something big, we should focus on one CM and not building various CM7. I don't know which is the point of this, and I don't know what were you thinking. In your github there is 0 changes on my device tree. I committed all my changes during the last month and you used my work to build your own, and then it seems that your ROM is better than mine, because I don't release mid-done ROM's. I want to give the best expierence to all the users.
Also, I committed all the changes to help people understand on what I'm working. Many users asked me if I was really working on it, as I did not commit anything to github, but I was. And what happens if I commit? other users use my work to build their ROM's? I think that's not the way to go.
And what about a simple credit to the real author of this ROM? as your signature says: Send me device tree and I'll build the ROM. Why? To be more famous using other people's work? I don't get the point of anything here...
Oh, btw, where are the permissions to do that?
Thanks, Biel.
bieltv.3 said:
Well, I don't know which is the point of this thread. You are building my sources. You are making my ROM. Why create another thread? You don't have the device, me neither, but I started that project from 0. Why instead of making your CM7 you don't help us? Why don't you make a pull request? Do we need to talk with testers, which are the same for the both of us, to just test the same ROM!? If we want to have something big, we should focus on one CM and not building various CM7. I don't know which is the point of this, and I don't know what were you thinking. In your github there is 0 changes on my device tree. I committed all my changes during the last month and you used my work to build your own, and then it seems that your ROM is better than mine, because I don't release mid-done ROM's. I want to give the best expierence to all the users.
Also, I committed all the changes to help people understand on what I'm working. Many users asked me if I was really working on it, as I did not commit anything to github, but I was. And what happens if I commit? other users use my work to build their ROM's? I think that's not the way to go.
And what about a simple credit to the real author of this ROM? as your signature says: Send me device tree and I'll build the ROM. Why? To be more famous using other people's work? I don't get the point of anything here...
Click to expand...
Click to collapse
Ok I am also starting the device tree from scratch. Is that alright?
I will suspend the current build and post a new one tomorrow which will based on my device trees.
About credits? I didnt even complete writing this thread..
About changes thing? I have made changes at my end which are not committed becuz I dont wanna put untested changes on github.
Sorry If I offended someone but I had no real intentions of doing that..
and btw.. I mean somehting else from my sign.. I want to help other device owners to get new roms to their device. Though it contradicts to this build.
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