Database Develop

kernel and rom pairing question

im on di11igafs 5.2 newest rom with Firebirds newest kernel flashed. I want to switch to SetrioNs kernel here for some good overclocking. I am unsure which to use and what the difference between his normal and XT versions are. i tried flashing the newest 1.6ghz XT SetrioNs but it freaked out my phone even in recovery menu after 20 seconds it would freeze up after about 20 seconds. Do i need to disable the lagfix in the recovery menu and or something else first? any help would be greatly appreciated . Thanks
Bryan

Your phone is not going to do 1600 no matter how hard you try.

newter55 said:
Your phone is not going to do 1600 no matter how hard you try.
Click to expand...
Click to collapse
/facedesk
Thats not what I asked about nor did I try to set it at 1.6 ghz. The phone wouldnt even boot long enough for me to change the voltage control settings. So I suppose i should rephrase my question so I dont get another answer like this one. I would like to use SetrioNs kernel, im using Firebirds kernel right now. Are there any steps i need to take in order to properly flash setrions kernel so that i dont have the problems I had previously?

newter55 said:
Your phone is not going to do 1600 no matter how hard you try.
Click to expand...
Click to collapse
Party pooper.

I know right? Woot woot.

Ok, sorry man. Honestly I would suggest downloading the Paragon rom and yanking the kernel out of that. It is much more up to date and allows oc.as high as 1.6. I have used that one without issue. Haven't tried setirons in quite a while so I don't know what may be going on.
Easiest way is to just put the rom zip in your sd card then use sgs kernel flashed app and select the rom zip. It will extract the kernel and flash it for you. Might want to disable lagfix first as sometimes problems occur when jumping back and forth between firebird and others.
Use voltage control 3.0 to control that kernel as well.

newter55 said:
Ok, sorry man. Honestly I would suggest downloading the Paragon rom and yanking the kernel out of that. It is much more up to date and allows oc.as high as 1.6. I have used that one without issue. Haven't tried setirons in quite a while so I don't know what may be going on.
Easiest way is to just put the rom zip in your sd card then use sgs kernel flashed app and select the rom zip. It will extract the kernel and flash it for you. Might want to disable lagfix first as sometimes problems occur when jumping back and forth between firebird and others.
Use voltage control 3.0 to control that kernel as well.
Click to expand...
Click to collapse
Ah! Thank You Thats exactly what i was looking for. I only have one question left. If i pull the kernel out of the rom will it be in .tar form? Thanks again

The kernel will be zimage. You can just copy that file straight to your sd card and the kernel flasher app will work with that as well.

Also it would seem that paragon is now using speedmods kernel. would you happen to be able upload the kernel you are using for me?

Give me a few.. have to get off the couch

here you go: http://dl.dropbox.com/u/11343737/zImage
Kernel from ParagonRC4

newter55 said:
Your phone is not going to do 1600 no matter how hard you try.
Click to expand...
Click to collapse
I got my phone OC to 1600 it was awesome...My screen couldn't handle it though. It froze

Stephenxda said:
I got my phone OC to 1600 it was awesome...My screen couldn't handle it though. It froze
Click to expand...
Click to collapse
you are lucky, usually they melt

What are you talking about here. I have my phone oc at 600Mhz and it works just fine. It is very stable and I have no issues with it.

newter55 said:
here you go: http://dl.dropbox.com/u/11343737/zImage
Kernel from ParagonRC4
Click to expand...
Click to collapse
Hey man thanks alot

no problem....sorry the humor in my original post didn't come through

newter55 said:
no problem....sorry the humor in my original post didn't come through
Click to expand...
Click to collapse
Haha not a problem. It just seemed like any post i made today i was getting sarcastic answers XD

[INT/Bell][CWM]Auto Ram Fixer for unlocked bootloader

Hi,
This is a small CWM zip to add the [email protected] line to your existing boot and recovery partitions to fix the ram issue with the international unlocked bootloader. If the second mem is already there it does nothing.
The point of this is you can have a regular recovery flashed and fix the ram issue without wondering what tegra part you have, it preserves your serial number as well. More useful with stock boot images than custom ones that already have this done.
To use:
Flash with a CWM recovery supporting edify scripting. That means you have an unlocked recovery basically.The program inside the zip can be used on it's own to list the cmdlines already in your phone, or to set them to something else.
As cmdline, it lists, as setcmdline it sets the entire thing, as addcmdline it adds on to the end of the existing cmdline.​Cheers!

Great! Looks like our bell friends are having good development as well.
Sent from my MB860 using XDA Premium App

NF, cheers bro I really appreciate the work from you.
Sent from my MB860 using XDA Premium App

So would i need to flash this once and then any ROM I install will have fixed RAM, or do I need to flash this after every installation?

IUH1991 said:
So would i need to flash this once and then any ROM I install will have fixed RAM, or do I need to flash this after every installation?
Click to expand...
Click to collapse
You can just keep it handy on your sdcard and use when needed, it depends on the "rom" you flash, it may or may not have a ram fix solution built in.
Cheers!

J-Roc said:
NF, cheers bro I really appreciate the work from you.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
You're welcome.
Cheers!

NFHimself said:
You can just keep it handy on your sdcard and use when needed, it depends on the "rom" you flash, it may or may not have a ram fix solution built in.
Cheers!
Click to expand...
Click to collapse
It depends on the Kernel the Rom has within it, nothing else.
Furthermore, no offense. But this is kinda useless now. Did you not know we have unified Kernel's? If someone made a Rom without a unified kernel, they can basically shove that Rom.
I do not see a point in this at all. I guess maybe for testing old Roms.....

NFHimself said:
You can just keep it handy on your sdcard and use when needed, it depends on the "rom" you flash, it may or may not have a ram fix solution built in.
Cheers!
Click to expand...
Click to collapse
So solid man, keep up the good work!

nexxusty said:
It depends on the Kernel the Rom has within it, nothing else.
Furthermore, no offense. But this is kinda useless now. Did you not know we have unified Kernel's? If someone made a Rom without a unified kernel, they can basically shove that Rom.
I do not see a point in this at all. I guess maybe for testing old Roms.....
Click to expand...
Click to collapse
Hi,
I addressed this already in the OP. It's more for use with stock kernels.
Can you compile the motorola kernel source (pick one) and get a binary exact match for the stock Bell kernel?
No offense to the guys working on kernel's here, but I am not really compelled by the added features/bug fixes, and am concerned more about stability, especially when the source seems to be ATT based. Which is fine if you are running an ATT framework "rom/theme" I guess, even better if you have an ATT phone.
Cheers!

NFHimself said:
Hi,
This is a small CWM zip to add the [email protected] line to your existing boot and recovery partitions to fix the ram issue with the international unlocked bootloader. If the second mem is already there it does nothing.
The point of this is you can have a regular recovery flashed and fix the ram issue without wondering what tegra part you have, it preserves your serial number as well. More useful with stock boot images than custom ones that already have this done.
To use:
Flash with a CWM recovery supporting edify scripting. That means you have an unlocked recovery basically.The program inside the zip can be used on it's own to list the cmdlines already in your phone, or to set them to something else.
As cmdline, it lists, as setcmdline it sets the entire thing, as addcmdline it adds on to the end of the existing cmdline.​Cheers!
Click to expand...
Click to collapse
Hi is this fix for when i flash IHOP and get ram problem it fix that or its universal for every kernel (Gb froyo ROMs etc) ?

so does this mean it is actually possible to download more ram??

xateeq said:
Hi is this fix for when i flash IHOP and get ram problem it fix that or its universal for every kernel (Gb froyo ROMs etc) ?
Click to expand...
Click to collapse
Yes, what you said.
Cheers!

geishroy said:
so does this mean it is actually possible to download more ram??
Click to expand...
Click to collapse
Uhm, what?
Cheers!

geishroy said:
so does this mean it is actually possible to download more ram??
Click to expand...
Click to collapse
Download more RAM? Umm...did you even read this before you posted it? or do you know absolutely nothing about what RAM is?

geishroy said:
so does this mean it is actually possible to download more ram??
Click to expand...
Click to collapse
So many people don't understand what Ram actually is *sigh*
You're not the first, I see it EVERYWHERE, google it up!

Thanks a lot, because i was having ram issue with eternity project kernel, and your patch solve it !
Sent from my MB860 using XDA App

dnsdenis said:
Thanks a lot, because i was having ram issue with eternity project kernel, and your patch solve it !
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Glad it worked out!
Cheers!

System Ram lists 816 total, so I should be in the clear or should I apply it anyways? Is there not a gig of ram on this thing or is some gpu/frame buffer dedicated?

drolgnir said:
System Ram lists 816 total, so I should be in the clear or should I apply it anyways? Is there not a gig of ram on this thing or is some gpu/frame buffer dedicated?
Click to expand...
Click to collapse
You are in the clear.
Cheers!

So, if I understand this correctly, when I flash this it will auto-fix any ROM, kernel or custom recovery that I install?

Required knowledge for building and mod Samsung GT-i9000 kernel

Hi, I would like to know what I have to learn in order to mod the stock kernel of GT-i9000, which last version (linux version 2.6.35) was written for the use in Gingerbread 2.3.6. My intention is to make it work in ICS or Jelly Bean Custom Roms, and then start tweaking and experimenting, but I need the basics first
I'm talking about knowledge specific to the kernel since I know how to make C programs and the structure of the android stack (Watched this someone? It's great!). Where I have to go? Websites specialized in the matter, ebooks to read, docs... By the moment I have downloaded and installed the CodeSourcery toolkit Samsung tells to install in the README file.
I expect to not completely brick my only sgs phone, but anyway I would like to know how to do it
EDIT: I edited a bit my question since I though it wasn't clear enough what I already know.

No one can help me? I don't expect to have the whole story, just to know what I have to learn :/ May be I'm not in the right subforum for this question. Full noob here at XDA xD

16bitboy said:
No one can help me? I don't expect to have the whole story, just to know what I have to learn :/ May be I'm not in the right subforum for this question. Full noob here at XDA xD
Click to expand...
Click to collapse
http://www.semaphore.gr/
I do not know, but the kernel is here and probably the best I know?

misacek said:
http://www.semaphore.gr/
I do not know, but the kernel is here and probably the best I know?
Click to expand...
Click to collapse
Yup but is not because I though there was no kernel. I know there are a lot, Devil's, Semaphore... I just want to do it by myself

No,Good work.:banghead:
Sent from my GT-I9000 using xda app-developers app

If you want to create a kernel for ics/jb, you should start with the default kernel of CM9/CM10, as most kernels for ics/jb are based on it. Then you could compare it to Semaphore, devil, ..., to see what they do differently.

[REQUEST] GB kernel

I'll try to do what I suggested at this post -> http://forum.xda-developers.com/showthread.php?t=2142591 .
But I need to know where I need to start. (Ok, I know where, but don't know HOW). Here it goes what I think, but I need help.
I have ideas, but don't know how to do all of them. So I need help, I need somebody there can help me. Give me some light. C_C
As I said, I wanna "split" gb kernel + cm9. Simple. But, how?
I need the droid 3 gb kernel, and I need a cm9 rom without the kexec kernel.
OR, (and I would very much appreciate) if some of our brilliant minds could expend just about 30 mins to explain to me how could I do it by myself.
ie:
Where I can extract, get, download the kernel. Or how I remove it from other place;
If the cm9 than i've downloaded came with kexec kernel, and how I remove it;
What I should do when I complete these steps;
*if there is a file (look how i'm losted! I even know if is a file, or a folder, .. buh ): ..).
pls. ):

giovannipaquier said:
I'll try to do what I suggested at this post -> http://forum.xda-developers.com/showthread.php?t=2142591 .
But I need to know where I need to start. (Ok, I know where, but don't know HOW). Here it goes what I think, but I need help.
I have ideas, but don't know how to do all of them. So I need help, I need somebody there can help me. Give me some light. C_C
As I said, I wanna "split" gb kernel + cm9. Simple. But, how?
I need the droid 3 gb kernel, and I need a cm9 rom without the kexec kernel.
OR, (and I would very much appreciate) if some of our brilliant minds could expend just about 30 mins to explain to me how could I do it by myself.
ie:
Where I can extract, get, download the kernel. Or how I remove it from other place;
If the cm9 than i've downloaded came with kexec kernel, and how I remove it;
What I should do when I complete these steps;
*if there is a file (look how i'm losted! I even know if is a file, or a folder, .. buh ): ..).
pls. ):
Click to expand...
Click to collapse
Im kinda lost at what your trying to do, you dont need a kernel to compile just cm9 really.
but if u want to try booting cm9 without the new kexec kernel3 just delete /system/etc/kexec folder and it will boot into 'stock' gb kexec kernel2 as long as you have safestrap installed
If you need the source for complete stock kernel hashcode has it hosted
https://github.com/Hashcode/solana_kernel
if you need the compiled kexec GB kernel im sure its in safestrap somewhere
You would probly need to make edits to cm9 though to make it work with gb stock kernel, it would be easier to use cm7 probly.

I wonder if Hash's old work on it is around?

jarveson said:
Im kinda lost at what your trying to do, you dont need a kernel to compile just cm9 really.
but if u want to try booting cm9 without the new kexec kernel3 just delete /system/etc/kexec folder and it will boot into 'stock' gb kexec kernel2 as long as you have safestrap installed
If you need the source for complete stock kernel hashcode has it hosted
https://github.com/Hashcode/solana_kernel
if you need the compiled kexec GB kernel im sure its in safestrap somewhere
You would probly need to make edits to cm9 though to make it work with gb stock kernel, it would be easier to use cm7 probly.
Click to expand...
Click to collapse
exaplaining, i wanna try to use cm9 without kexec kernel, 'cause still with bugs. i saw this post, and after read it all, i thinked if it's not possible do it again. at this post, was posted a cm9 rom, working fine, without bugs. BECAUSE it wasn't with kexec kernel, but with gb kernel.
but the links is off, and ill try to do it by myself. and looking your simple explanation, i'll try and post results, being good or not. but i still have some questions.
1 - as you said, i need to make what kind of edits?
2 - at cm7, what & how i suppose to act?

giovannipaquier said:
exaplaining, i wanna try to use cm9 without kexec kernel, 'cause still with bugs. i saw this post, and after read it all, i thinked if it's not possible do it again. at this post, was posted a cm9 rom, working fine, without bugs. BECAUSE it wasn't with kexec kernel, but with gb kernel.
but the links is off, and ill try to do it by myself. and looking your simple explanation, i'll try and post results, being good or not. but i still have some questions.
1 - as you said, i need to make what kind of edits?
2 - at cm7, what & how i suppose to act?
Click to expand...
Click to collapse
I hate to break it to you, but that cm9 is not fully functional and without bugs. Just off the top of my head I know it has no camcorder, and no HW codecs and while the photo camera works, it's a hack and takes forever to open and can't be used for secondary functions like scanning QR codes. Also I'm pretty sure battery life is ****. And I believe it has the mediaserver battery drain bug, where if you listen to music it will drain your phones in 2-3 hours, tops
And this is just what I can think of, it's been quite some time since I've ran it. If you're determined, I can check to see if I have it kicking around in my Linux files later, but i wouldn't hold your breath.
I don't want to discourage you from trying to learn more about android hacking and dev, but based on your posts I don't think you have the knowledge to fix cm9, I know I don't.
I know it would be great to have a fully functional better than gingerbread rom, but I'm afraid it's GB or beta.
Sent from my DROID3 using xda premium
---------- Post added at 03:36 PM ---------- Previous post was at 03:31 PM ----------
Cm7 was mostly functional, and I'm pretty sure I have that, but it never worked for the xt860 properly, mobile connection issues. Personally I think it's the libmoto_ril.so, or something in the build.prop, or both. Look into what other moto devices use the same radio as the xt860 and if they have cm7
Sent from my DROID3 using xda premium

Endoroid said:
I don't want to discourage you from trying to learn more about android hacking and dev, but based on your posts I don't think you have the knowledge to fix cm9, I know I don't.
I know it would be great to have a fully functional better than gingerbread rom, but I'm afraid it's GB or beta.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
wait, .. how? lol
i know i can't FIX cm9, wtf, who I am to say something so stupid?
i didn't mean this. sorry if i looks like yes.
based on your posts I don't think you have the knowledge to fix cm9
Click to expand...
Click to collapse
i know i don't have it. at ALL my posts, i think i never forgot to say something to confirm it. and like i always says, i know i'm dumb, i ALWAYS assume it, being sayin' it exactly or at other words.
but, it's not to look like something crazy, like somebody who needs atention and bla bla bla. just the true.
and another true is there i wanna try, i wanna learn, i need to try, i need to learn. i think something really nice is about to come.
Sent from my XT860 using xda app-developers app

here is a cm9 that i'm fairly sure is non kexec
https://www.dropbox.com/s/72jk7id8hnkl9c7/cm9-droid3-20120130-1730.zip
and here is cm7
http://d-h.st/lzD

Endoroid said:
here is a cm9 that i'm fairly sure is non kexec
https://www.dropbox.com/s/72jk7id8hnkl9c7/cm9-droid3-20120130-1730.zip
and here is cm7
http://d-h.st/lzD
Click to expand...
Click to collapse
Anyone try this?
Sent from my DROID3 using xda app-developers app

i'll try it.

Neither of these will work on an xt860 out of the box. (i mens they will, if you don't want any cellular servicd) I'm only posting Because giovannipaquier has asked for these.
Sent from my DROID3 using xda premium

at cm9, camera doesn't works.
safestrap 3.05 with cm7 just give me black screen. tried with milestone3bootstrap and bricked. ):
unbricked right now.

Endoroid said:
Neither of these will work on an xt860 out of the box. (i mens they will, if you don't want any cellular servicd) I'm only posting Because giovannipaquier has asked for these.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
what you mean is there it works, but i'll not have gsm?
i've got fc's on phone app at startup.

Building a new kernel need some info

Ok guys i am building a new kernel for you Note users based on the official source that samsung Dropped..i have the source and tools the problem is can someone point me on how to include the recovery as i do not own the device and would like to share some love on this device..else i will just build it without the recovery..
your replies will be much appreciated as this will be step forward for you to have a new kernel..this will be a blind build since i do not own the device i DID own it but never fiddled with it since the device was prone to bricking..

I hope you are aware of the brick bug.
http://forum.xda-developers.com/showthread.php?t=1633943
http://forum.xda-developers.com/showthread.php?t=1857556

Boy124 said:
I hope you are aware of the brick bug.
http://forum.xda-developers.com/showthread.php?t=1633943
http://forum.xda-developers.com/showthread.php?t=1857556
Click to expand...
Click to collapse
He just said that lol
Sent from my Galaxy Nexus using xda premium

Boy124 said:
I hope you are aware of the brick bug.
http://forum.xda-developers.com/showthread.php?t=1633943
http://forum.xda-developers.com/showthread.php?t=1857556
Click to expand...
Click to collapse
yes i am aware of that and it seems the newer ones are now safe from brick bug..but still its never late just to be cautious..

just finished building 1 kernel image..hope i did it right..
note: Always do a backup before borking your device..
test zimage
also i need a clean ramdisk for STOCK TW roms..as i am just using the Revived Hydracore kernel ramdisk..it might not boot as i what i am seeing it..but nonetheless just try if it boots up..

kairi_zeroblade said:
yes i am aware of that and it seems the newer ones are now safe from brick bug..but still its never late just to be cautious..
Click to expand...
Click to collapse
Sorry, but that's kind of a joke: you want to build a kernel for the Note, but you do not have one. And you do not know how to include recovery. And you want to be cautious.
You really expect that a member with a Note would risk his device testing this?
Maybe you should start to build a kernel for a device you own yourself.

ThaiDai said:
Sorry, but that's kind of a joke: you want to build a kernel for the Note, but you do not have one. And you do not know how to include recovery. And you want to be cautious.
You really expect that a member with a Note would risk his device testing this?
Maybe you should start to build a kernel for a device you own yourself.
Click to expand...
Click to collapse
i used the remaining Hydracore remnants for ramdisk and in my inspection i did found a recovery included..nevertheless it seems to be safe as i am reading his deve post before i dived in..
i own an S3 and i built my own kernel for it..based on the Update 7 sources the same goes for my S3 mini(i do not own the device but since sources are available then why not build 1)..also i am not obliging everyone to help..if it boots up then good for you as i can upload the source and for your devs to start spinning things..much more or less its a good start..
you can always ODIN in the stock boot image..if things come worse..also do not blame me since this was the problem with samsung to begin with..
edit1: ok so for those who are interested to help me you can PM me as i want to try the lower exynos platform..this is just weird as the kernel format is in zimage instead of a normal boot.img file..this is just for those who are brave and knows the way around stuff with N7000..

kairi_zeroblade said:
you can always ODIN in the stock boot image..if things come worse..also do not blame me since this was the problem with samsung to begin with..
Click to expand...
Click to collapse
If things come worse you'll make a new "Angelom Kernel". No risk for you - because you can't brick your device.
But in the end each tester has to decide if he wants to test your "blind build".

ThaiDai said:
If things come worse you'll make a new "Angelom Kernel". No risk for you - because you can't brick your device.
But in the end each tester has to decide if he wants to test your "blind build".
Click to expand...
Click to collapse
that is why its just for those who are brave enough..else you stay on stock forever..that is why samsung release these codes..for those who are interested..else just look at those codes..