Develop Bugs

i would like to build my own kernel but i am not able to.. help me pls

I would like to build my i9000's kernel but there are problems
I've installed ubuntu 9.10.
As you know, i could download the source code from the web
In that there are codes for making kerne
and also there is a script, named build_kernel, which makes me be able to build the kernel.
At first, i installed sourcery toolchain and then modified the build_kernel.sh
Because the instruction said i should change toolchain's directory and prefix
And finally i built it writing './build_kernel.sh'.
It seemd to be working but there were so many errors
And the zimage file was small, it's only 2.1MB
I tried to flash that kernel but it made my phone go black.
Can anyone help me please?
What should i do?
How did some people make such great kernels? Sorry im newbie.

dkcldark said:
I would like to build my i9000's kernel but there are problems
I've installed ubuntu 9.10.
As you know, i could download the source code from the web
In that there are codes for making kerne
and also there is a script, named build_kernel, which makes me be able to build the kernel.
At first, i installed sourcery toolchain and then modified the build_kernel.sh
Because the instruction said i should change toolchain's directory and prefix
And finally i built it writing './build_kernel.sh'.
It seemd to be working but there were so many errors
And the zimage file was small, it's only 2.1MB
I tried to flash that kernel but it made my phone go black.
Can anyone help me please?
What should i do?
How did some people make such great kernels? Sorry im newbie.
Click to expand...
Click to collapse
check few threads behind you ... it is illustrated in the links.

SenseUI and MotoBlur on Galaxy S

I got myself a Galaxy S to play with now, and so far the good part is the nice screen...
ive done some porting to motorola milestone which i will start looking into on this phone...
As i understand Kernel can be customized and we can pretty easily install mods using update.zip ?
is updating ramdisk "easy"? if you can handle linux quite well? anyone with instructions on building the initrd image?
secondly building an image? should it be tar'd using odin? or using update.zip?
problems on milestone has been "usb" steeling battery as the native support on htc is different so handling it required a scripting workaround..
with senseui the biggest problem will be porting Bluetooth as it is very different from standard google practice...
anyways i hope to be able to contribute with a SenseUI and MotoBlur port to SGS soon, when i get time to research handling on this model.

i'd really like to help you, but i'm not able... this morning i studied some tutorial such as http://pdk.android.com http://android.git.kernel.org http://d.android.com, but i'm new with linux and i can't understand anything... however i was asking myself the same questions...

Quick catch-up:
Dexter_nlb said:
As i understand Kernel can be customized and we can pretty easily install mods using update.zip ?
Click to expand...
Click to collapse
Check, Possible: http://forum.xda-developers.com/showthread.php?t=767431
Dexter_nlb said:
is updating ramdisk "easy"? if you can handle linux quite well? anyone with instructions on building the initrd image?
secondly building an image? should it be tar'd using odin? or using update.zip?
Click to expand...
Click to collapse
Well, IDK if this easy, but manageable. Both odin (easier) and update.zip (more stable) options available.
Dexter_nlb said:
problems on milestone has been "usb" steeling battery as the native support on htc is different so handling it required a scripting workaround..
with senseui the biggest problem will be porting Bluetooth as it is very different from standard google practice...
anyways i hope to be able to contribute with a SenseUI and MotoBlur port to SGS soon, when i get time to research handling on this model.
Click to expand...
Click to collapse
You could contact people at #project-voodoo to get more detailed information.
Best of luck.

Dexter_nlb said:
I got myself a Galaxy S to play with now, and so far the good part is the nice screen...
ive done some porting to motorola milestone which i will start looking into on this phone...
As i understand Kernel can be customized and we can pretty easily install mods using update.zip ?
is updating ramdisk "easy"? if you can handle linux quite well? anyone with instructions on building the initrd image?
secondly building an image? should it be tar'd using odin? or using update.zip?
problems on milestone has been "usb" steeling battery as the native support on htc is different so handling it required a scripting workaround..
with senseui the biggest problem will be porting Bluetooth as it is very different from standard google practice...
anyways i hope to be able to contribute with a SenseUI and MotoBlur port to SGS soon, when i get time to research handling on this model.
Click to expand...
Click to collapse
Samsung is using a zImage. Compressed Kernel + Initramfs.
Since for 2.2 is no Sourcecode available till now, it's very hard to modify anything.
2.1 Source is available at opensource.samsung.com.
You can pack the zImage with tar under linux and flash with odin or you can flash the Image directly using redbend_ua (OTA Update) through an update.zip.

Aery said:
Samsung is using a zImage. Compressed Kernel + Initramfs.
Since for 2.2 is no Sourcecode available till now, it's very hard to modify anything.
2.1 Source is available at opensource.samsung.com.
You can pack the zImage with tar under linux and flash with odin or you can flash the Image directly using redbend_ua (OTA Update) through an update.zip.
Click to expand...
Click to collapse
thanks , very usefull.. so the .md5 extension on odin files are related to?
anyways i have made zImage for other platforms so changing the ramfs should be straight forward...

Finally a person who knows their stuff is attempting at a sense ui port.
Hope you succeed

I really hope you succeed - I have time but no knowledge - if you need help pm me

DesireHD rom? YES PLEASE!!!

I'll happily donate if you create a Bounty Thread here, if you do get down and serious about it.

MAMBO04 said:
I'll happily donate if you create a Bounty Thread here, if you do get down and serious about it.
Click to expand...
Click to collapse
Same here.

MAMBO04 said:
I'll happily donate if you create a Bounty Thread here, if you do get down and serious about it.
Click to expand...
Click to collapse
thanks, im primarily persuing this as a personal challenge, but of course if ppl likes my work its great.
one note is, as written earlier, more experienced guys will be required to finish the bluetooth adaption, its alot more complex than the remaining parts.
and im told even on older htc phones it was hard to port drivers for bt.
my 2.1 sense mod on milestone was ok, except milestone only had 256MB, which resulted in many reloads of senseui.. here i think we can stabilize, even with a modified kernel to add swap if needed (if the 512MB utilization becomes a problem)

I would be very interested in a Desire HD rom for the SGS .
If it is completely functional for all the functions I use (I use no Bluetooth for example), I would be willing to donate too.
xan said:
You could contact people at #project-voodoo to get more detailed information.
Click to expand...
Click to collapse
+1.
It's on the Freenode IRC servers. There's a bunch of talented developers working on improvements for the SGS there, so be sure to drop by.

jjwa said:
I would be very interested in a Desire HD rom for the SGS .
If it is completely functional for all the functions I use (I use no Bluetooth for example), I would be willing to donate too.
+1.
It's on the Freenode IRC servers. There's a bunch of talented developers working on improvements for the SGS there, so be sure to drop by.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=8254744#post8254744
A thread for bounty to devs porting for SGS succeed
-Fraction

Aery said:
Samsung is using a zImage. Compressed Kernel + Initramfs.
Since for 2.2 is no Sourcecode available till now, it's very hard to modify anything.
2.1 Source is available at opensource.samsung.com.
You can pack the zImage with tar under linux and flash with odin or you can flash the Image directly using redbend_ua (OTA Update) through an update.zip.
Click to expand...
Click to collapse
Wasn't the JPM source leaked for a little while about a week back? Is that the source code to which you're referring?
Edit: Sorry forgot to check the post date, so at the time you posted that, the source code had not been leaked

[Q][Help] B5510 - Building Kernel/boot.img Problem

Hi there.
First: Im a noob, so unless i have fewer than 10 posts i can only post in general forum - otherwise i would post on an existing thread (i will mention later).
Last week i got a new phone: Samsung Galaxy Y Pro (GT-B5510).
Its a nice phone, but im missing a thing: a firewall.
I tried droidwall and other, but they arnt working. So there is something wrong with the netfilter/iptables modul and ive to rebuild the kernel.
After a quick search i found this thread and this post.
I already set up a Ubuntu (10.04.4), downloaded the source from samsung and the toolchain from Sourcery (like they mention inthe infofile from samsung).
I build the kernel, like irfanbagus in his post, but for my device.
I got lots of compilerwarnings, but in the end i have had my zImage without errors.
I split my boot.img, which i got from my device with Terminal Emulator, with split_bootimg.pl.
Now ive got a kernelimage and a initrd and ive to put them together.
Presumably with mkbootimg, but ive to know the baseadress.
I tried the offset from the thread mentiond above.
I made a tar and flashed it with Odin1.85 and half bricked it.
[I only can see a grey battery on the diplay and if i reboot it it stuck on bott/splashscreen]
Maybe somebody can help. (please)
Is the problem the compiled kernel, due to the warnings?
Or is it the wrong baseaddress? Well i could not find the address inside the sourcecode (like kconfig), like i read somewhere, thats why i tried the one from s5360.
There is no problem with odin or the cable, cause i can flash my backup with it to 'unbrick' it.
And why is the bootimg around 700kb smaller than the original?
Thanks a lot in advance.

havocinside said:
Hi there.
First: Im a noob, so unless i have fewer than 10 posts i can only post in general forum - otherwise i would post on an existing thread (i will mention later).
Last week i got a new phone: Samsung Galaxy Y Pro (GT-B5510).
Its a nice phone, but im missing a thing: a firewall.
I tried droidwall and other, but they arnt working. So there is something wrong with the netfilter/iptables modul and ive to rebuild the kernel.
After a quick search i found this thread and this post.
I already set up a Ubuntu (10.04.4), downloaded the source from samsung and the toolchain from Sourcery (like they mention inthe infofile from samsung).
I build the kernel, like irfanbagus in his post, but for my device.
I got lots of compilerwarnings, but in the end i have had my zImage without errors.
I split my boot.img, which i got from my device with Terminal Emulator, with split_bootimg.pl.
Now ive got a kernelimage and a initrd and ive to put them together.
Presumably with mkbootimg, but ive to know the baseadress.
I tried the offset from the thread mentiond above.
I made a tar and flashed it with Odin1.85 and half bricked it.
[I only can see a grey battery on the diplay and if i reboot it it stuck on bott/splashscreen]
Maybe somebody can help. (please)
Is the problem the compiled kernel, due to the warnings?
Or is it the wrong baseaddress? Well i could not find the address inside the sourcecode (like kconfig), like i read somewhere, thats why i tried the one from s5360.
There is no problem with odin or the cable, cause i can flash my backup with it to 'unbrick' it.
And why is the bootimg around 700kb smaller than the original?
Thanks a lot in advance.
Click to expand...
Click to collapse
upload your boot.img

boot.img
Here it is.
boot.tar = compiled
boot-stock.tar = original from my device

Size is not problem as long running well.
In my sgy always fail when size >
5.5mb
For boot-stock.tar u get from dd or pda stock-rom ??
Mmm i thing irfan has answer so ur save dude.

its dd.

i don't find any problem with boot.img. offset is equal (0x81600000). the problem maybe in your zImage. make sure you build with correct defconfig. mine is bcm21553_totoro_05_defconfig, i don't know yours, see in text info inside zip file from samsung. and make sure using the same compiler version with text info said. using different version make prebuild kernel module inside initramfs not working. start with default config from xxx_defconfig just to make sure your step is correct. and if still not working your best hope is build your module as loadable module (.ko), add init.d support in init.rc (inside initramfs), and load your module using init.d script.
about the size, it's nomal boot.img from dd command bigger than normal boot.img because it's copy whole partition and include unused bytes behind the original boot.img.

hm, ok.
thank you irfan.
i followed the instructions from the txt inside the archive:
"bcm21553_luisa_03_defconfig" with "g++ 2009q3-68 arm eabi"
ill try again.

my bad. i download wrong files, and end up with comparing the same original boot.img
your compiled boot.img don't have md5 checksum. i am not sure it have effect, i make that tutorial based post from harish2704 here. mkbootimg from harish2704 have --kernelMD5 param. try use that one.

savie said:
Size is not problem as long running well.
In my sgy always fail when size >
5.5mb
For boot-stock.tar u get from dd or pda stock-rom ??
Mmm i thing irfan has answer so ur save dude.
Click to expand...
Click to collapse
our kernel partition only 5 mb my friend...

Boot.img from dd not work with me so i pick from pda stock-rom
(i use from doky thread).
Mmm that why i fail when boot.img more than 5mb.
Trying other method to compile, irfan say merruk use lzma or someting like that.

I can only suggest the method irfanbagus described (loadable kernel modules) because the source code Samsung released probably isn't up to date. The benefits of compiling the needed modules into the kernel are too little compared with possible bugs which are in the released code but not in the stock kernel.

mikstev said:
I can only suggest the method irfanbagus described (loadable kernel modules) because the source code Samsung released probably isn't up to date. The benefits of compiling the needed modules into the kernel are too little compared with possible bugs which are in the released code but not in the stock kernel.
Click to expand...
Click to collapse
i find relative new kernel for sgy, but still cannot make running. it's from galaxy pocket source. there is small change related to power management, but still don't have time to studying.

After a weekend full of trouble, today i found time to continue the bootimg-thing.
I now compiled only the modules and load them now with initd, because i was unable to build a runnable kernel from source.
(Thank you irfan and mikstev)

irfanbagus said:
i find relative new kernel for sgy, but still cannot make running. it's from galaxy pocket source. there is small change related to power management, but still don't have time to studying.
Click to expand...
Click to collapse
are you sure that we can use that kernel for our sgy?

boot image

Can somebody explain me the proper way to build the boot image? I'm able to build a pure kernel image but i'ts now what i need to flash into boot partition.

Eh that's a bit complicated, the kindled booting is a uniqueish format. Hashcode made a custom make setup in cm's build system to put it together since it not only has a weird signature but a second bootloader added onto the beginning of it as well. Are you compiling a rom or just trying to rebuild the bootimg?
Sent from my LG-P769 using Tapatalk

Yeah, I've tried to figure out from the CM port how it's built. I've found some code here:
https://github.com/KFire-Android/android_device_amazon_jem/blob/cm-11.0/boot.mk
But I can't figure out how to attach a kernel image, ramdisk, what else.
I'm not building rom, just want to change some features in the stock kernel.

I could attempt to throw one together for you, I think my current setup doesn't bother to check the intramfs as long as it exists in the out directory, I'd just have to replace the kernel and initramfs and attempt a build. O wait I'm in the 8.9" section, I don't have a working build of b2g going for that yet, probably wouldn't be the best idea, would probably work but Idk. You could just build cm from source and pull the bootimg out of the zip it makes. Maybe I can slap together some instructions, I kinda see in the makefile how it works but makefile scripting isn't my forte, its similar to bash but different enough i can get confused at points.
Sent from my Amazon Tate using Tapatalk

Building the whole cm is a bit overhead. I don't need the complete build script but it would be great if you point out some makefiles, or places to look in the source tree, i'll try to fugure out how to use it.

So anyone?

ipipipipip said:
So anyone?
Click to expand...
Click to collapse
ah sorry i have been at work most of the week and passing out once i get home (thank you low stamina). Anyways i thought i had posted something on here about where to look but it seems i didnt, look at this file: https://github.com/KFire-Android/android_device_amazon_jem/blob/cm-11.0/boot.mk#L27
That area (line27ish) should give you the hints you need.
Edit: wait this is a 8.9, wrong link, that would be a nice brick if that was used... Fixed!
most of that file makes sense, the only thing i am unfamiliar with is [email protected] $ usually means a variable or something else i'm trying to rember involving a program, probably storing output from a program as the variable. As to the @ symbol i have heard it means array, not very sure at all about how it works.

Compile COJ3 from source N910F

Hello friends,
I wanted to start kernel developing for the N910F. So i wanted to start compiling the original samsung sources.
Please excuse me, I'm pretty new to android/linux development.
I managed to get the kernel compiling, which gives me an output folder with some GB of stuff and as i could point out a zImage-file, which is hopefully the compiled kernel
To get my kernel working, extracted a stock boot.img with umkbootimg, which gave me a warning, that i can't repack the boot.img without using a modified mkbootimg executable.
A mkbootimg is included in the sammy-source so i used this to pack my zImage together with the extracted initfs.gz, resulting in a boot.img.
Which I flashed ofc, but the reason why i opened this thread is the result of this
The kernel is obviously not booting, it shows for maybe 0.5s the sammy logo and directly starts into download mode.
I guess it has something todo, how i pack my kernel. because i didnt even manage to unpack the stock kernel and repack it and get it booting.
So where is my mistake? Do i miss something?
greez d4rk

Deleted - I notice I replied to an old thread