Database Develop

Kernel compilation for Samsung Galaxy S I9000

Hi all,
we are trying to build our own kernel for a Samsung Galaxy S (I9000XWJVB).
What we did so far:
- Download the correct sources from "opensource.samsung.com"
- Studied the README
- Installed cross-compiler toolchain
- Created ".config" as described in README
- Kernel compiled
Compilation worked fine -> zImage was available (but with only 2mb very)
OK, looks like initramfs is missing.
The first question is now, where to get / how to create a correct initramfs?
We copied the initramfs from Leshak and we extracted an ".cpio" from a working zImage.
Then we tried to use them in the ".config" (CONFIG_INITRAMFS_SOURCE) for kernel compilation.
Resultant zImage was larger (around 6mb) so it looks like something changed.
But once we installed the tared zImage on the phone (using Odin), the phone freezes during reboot.
Any advice how to progress here?
Is it possible to use Leshaks initramfs for all Galaxy S phones? Or is this only for a specific version? The CONFIG_INITRAMFS_SOURCE should point to the "initrd.arm.initramfs_list", correct? And not to the initramfs-folder?
And: Is there a way to get any type of kernel boot debugging message from the booting phone back to the PC (or the phone screen)?
Many thanks in advance!

I don't know much about kernels. But i will try to help. Have you tried other itiramfs or reconfig them?
There are not many people that will know answer so ask some kernel developers like hardcore, supercurio...
Sent from my GT-I9000 using XDA Premium App

Just saw 2nd question. I think that it should point to intiramfs folder. You can zip all kernel files and upload it so i can take a look at them
Sent from my GT-I9000 using XDA Premium App

Hi,
themate1987 said:
I don't know much about kernels. But i will try to help. Have you tried other itiramfs or reconfig them?
There are not many people that will know answer so ask some kernel developers like hardcore, supercurio...
Click to expand...
Click to collapse
we tried four different initramfs now, but ended up always with a freezing phone.
I would like to ask the kernel experts directly, but I'm new to this forum and not allowed to post in the developers forums. I hope that one of the gurus will reply to this thread.
themate1987 said:
Just saw 2nd question. I think that it should point to intiramfs folder.
Click to expand...
Click to collapse
My understanding is that the .list file will describe the structure of the initramfs folder and if this file is present, it should by used in the .config. Otherwise the .config should point to the folder.
Please correct me if I'm wrong.
But anyway, we tried both versions, none worked.
Regards!

PM some kernel developers
Sent from my GT-I9000 using XDA Premium App

Use speedmod kernel patches with the readme file he has given..
or else you can go through supercurio threads also ...
they explained the kernel compilation methods....
thanks

Did you get this to work finally? I too am trying to compile and flash a custom kernel ( For SGS4G) I point my INIIRAMFS_SOURCE to an extracted initram dir, but the resulting boot zImage does not proceed past the initial boot screen(s) Please let me know if you succeeded, and if yes, how.
Thanks!

What I got the problem was about initramfs.cpio.
At that moment , the most important point you know is you should make the file in Linux..
When my friend made me a file is initramfs.cpio , it worked well.
But what I made in window made always troubles for compile.
So if you made a initramfs.cpio with hexeditor in window, try it in Linux again..
Thx!

[GUIDE] dsixda's Android Kitchen - Now supports GS3 I9300 (Windows/Linux/Mac)

dsixda's Android Kitchen - Now for Samsung Galaxy SIII GT-I9300
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy SIII GT-I9300(T) custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of the latest versions, you can now create your own Galaxy S3 I9300 ROMs with the kitchen.
NOTE: This guide may also work for other Samsung devices. So if you were told to come here and you have a different device, it was not an error - just make sure you use a base ROM from your own device, not from the I9300! For all other Galaxy S3 variants, this guide might not be exactly the one you're looking for. There may be support for your S3 device in the kitchen, but I'd need to post different instructions. Check the first post of the kitchen thread for any updates for linked instructions.
I'd like to thank klander for testing and providing feedback, which is always appreciated!
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
​
PROCEDURE FOR MAKING YOUR ROM:
NOTE: If you have a non-I9300 device and were told to follow these instructions, then use a base ROM from that device, NOT a ROM meant for the I9300!! The same steps below, however, (and common sense) should be used.
First, you need a rooted Samsung Galaxy S3 I9300 with a custom recovery menu, which allows flashing of custom ROMs.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows, Linux or Mac OS X. Ensure you read the FAQ carefully.
Put one or more of your base ROM(s) under the original_update folder. For the Samsung Galaxy S3 I9300, there is support for the following formats (that I know of) which can be placed in that folder:
Stock firmware:
system.img, boot.img, cache.img (and optionally: modem.bin)
TAR/ZIP file containing the above. NOTE: If the TAR file name ends with "MD5", remove the MD5 part from the name.
OR Custom ROM:
must be a ZIP file created by the kitchen from the stock firmware (NOTE: The kitchen may NOT support custom ROMs created through other methods such as CyanogenMod, due to potential file structure incompatibility issues)
OR Nandroid backup from custom recovery image:
system.img, cache.img and boot.img
system.ext4.tar, cache.ext4.tar and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
Root your ROM
Add Busybox
Optional: Disable boot sounds
Optional: In the Advanced options menu: De-odex your ROM (your mileage may vary as to whether this works 100%)
Optional: Add or remove the modem.bin from your working folder
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin. Make a Nandroid backup of your current system before you flash anything!
Some notes:
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
For the benefit of other readers and to prevent confusion, please only discuss the Samsung Galaxy SIII GT-I9300 in this thread!
Most of all, have patience, take your time and enjoy!!

just what i need

I have a de-bloat script if you want a copy to convert to a kitchen script. It's perl calling system values and the kitchen.
Are we still meant to be extracting the img files manually to get them working?

Kangburra said:
I have a de-bloat script if you want a copy to convert to a kitchen script. It's perl calling system values and the kitchen.
Click to expand...
Click to collapse
I'm not doing additional work, but if you'd like you could make a plugin for the kitchen, which would go under the /scripts/plugins folder and can be accessed from the Advanced menu of the kitchen. I can advertise it in the kitchen thread (in the plugins section) as a separate download under your name.
Are we still meant to be extracting the img files manually to get them working?
Click to expand...
Click to collapse
With Cygwin the kitchen will give you instructions on which program to open and how to use it (manually). The programs are found in the kitchen.
With Linux/Mac, it is all automated and very quick.

Just when I thought this kitchen was a goner, you came along and made it work again

I have just put the French zip into the kitchen and it fails to extract the img files.
Available ROMs:
(1) I9300XXDLIH_I9300VFGDLJ1_SFR.zip
Enter selection number (default=1, cancel=0, r=refresh):
Selected I9300XXDLIH_I9300VFGDLJ1_SFR.zip
The new working folder will be named WORKING_101712_171605
Change the name (y/n)? (default: n):
Creating working folder WORKING_101712_171605 ...
Extracting ROM ...
Error: No system folder found!
Press Enter to continue
Click to expand...
Click to collapse
It works after manually extracting so no big deal

Kangburra said:
I have just put the French zip into the kitchen and it fails to extract the img files.
It works after manually extracting so no big deal
Click to expand...
Click to collapse
If the zip contains a tar file then it's not going to work, you need to unzip the tar file.

The best tool for deodex Roms!
THANKS dsixda! :good:
Regards
adesirello (AndyX ROM)

Awesome job mate :good:

tomorrow`s homework !
thanx !

Perfect! Just two days ago i was think at dsixda kitchen! I don`t have enough thanks for this!

Great.
Just what i was looking for.

dsixda said:
dsixda's Android Kitchen - Now for Samsung Galaxy SIII GT-I9300
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy SIII GT-I9300(T) custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of the latest versions, you can now create your own Galaxy S3 I9300 ROMs with the kitchen.
IMPORTANT: For all other Galaxy S3 variants, this guide may not be exactly the one you're looking for. There may be support for your S3 device in the kitchen, but I'd need to post different instructions. Check the first post of the kitchen thread for any updates for linked instructions.
Click to expand...
Click to collapse
just wanted to let u know that when cooking my rom with ur kitchen, awesome by the way, i was getting constant hang at logo on boot. i went back to the beginning as it worked and booted and just added bit by bit until i found the issue. the issue was adding busybox install run parts. it took me a day to figure this out. i went through kernel to framework and nothing fixed this issue where booting just to logo then stuck. finally deleted working folder, went back to a basic rom, slowly added root, then busybox, deodex etc. i dont know if this issue is specific to just me and my particular build but just putting it out there for others wanting to use this excellent kitchen on their i9305.

L335K1 said:
just wanted to let u know that when cooking my rom with ur kitchen, awesome by the way, i was getting constant hang at logo on boot. i went back to the beginning as it worked and booted and just added bit by bit until i found the issue. the issue was adding busybox install run parts. it took me a day to figure this out. i went through kernel to framework and nothing fixed this issue where booting just to logo then stuck. finally deleted working folder, went back to a basic rom, slowly added root, then busybox, deodex etc. i dont know if this issue is specific to just me and my particular build but just putting it out there for others wanting to use this excellent kitchen on their i9305.
Click to expand...
Click to collapse
Did you create a /system/etc/init.d folder with your custom scripts after enabling the Busybox Run-parts? That option is quite old but I have not seen anyone try or test it with any of the Galaxies. Maybe when you have time next time, do a logcat while it boots and see what the problem is (assuming you had the init.d folder created already). Thanks

dsixda said:
Did you create a /system/etc/init.d folder with your custom scripts after enabling the Busybox Run-parts? That option is quite old but I have not seen anyone try or test it with any of the Galaxies. Maybe when you have time next time, do a logcat while it boots and see what the problem is (assuming you had the init.d folder created already). Thanks
Click to expand...
Click to collapse
yea i created the init.d folder first, (using v29 so it gives u warning anyways), but it still does this. i have to add init.d support manually through my script. but this is awesome, i just gotta remember not to use that feature.. i did both logcat and recovery logs but couldnt make heads or tails of it. it was easier to go back through ur kitchen, add 1 feature at a time until i found the culprit. thanks heaps

Please link to download the kitchen, thank you very much.

misacek said:
Please link to download the kitchen, thank you very much.
Click to expand...
Click to collapse
First post.

This is great!
Thanks dsixda.
YZ.

Please not see me? can give direct link? thank you very much

misacek said:
Please not see me? can give direct link? thank you very much
Click to expand...
Click to collapse
If you refuse to or are unable to read post #1 then you'll have trouble using - and even installing - the kitchen.

[GUIDE] dsixda's Android Kitchen - Now supports Galaxy Note GT-N7000 (Win/Linux/Mac)

dsixda's Android Kitchen - Now for Samsung Galaxy Note GT-N7000
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy Note GT-N7000 custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of the latest versions, you can now create your own Galaxy Note GT-N7000 ROMs with the kitchen.
To my surprise, since the file structure is very similar to that of the Galaxy SII GT-I9100, I only had to make a very minor update to the kitchen (one blank file) to allow GT-N7000 support.
Special thanks to long-time XDA user Ameet for testing and providing feedback!
I have already posted an equivalent guide for the Galaxy SII I9100, so no need for redundancy. The same steps will work for your device:
CLICK HERE FOR KITCHEN INSTRUCTIONS FOR YOUR GALAXY NOTE GT-N7000.​http://forum.xda-developers.com/showthread.php?t=1227549
NOTE: This guide does not apply for the other models of the Galaxy Note; there is a separate thread for the SGH-I717.
Since the above link is for I9100 discussion only, please post all N7000 talk in the thread right here. Enjoy!
​

So good to see you here. Welcome.

chasmodo said:
So good to see you here. Welcome.
Click to expand...
Click to collapse
Thanks, I don't have the device but I have its little brother, the Exynos-based Galaxy SII GT-I9100

Thanks for coming over. I have actually been using it on the Note for a long time. Its a great tool. Thanks for developing it mate

Thanks for this...
Sent from my GT-N7000 using Tapatalk 2

Awesome work as always Dsixda, as always.. Am sure this will be of great help for Note users
Sent from my GT-N7000 using xda premium
---------- Post added at 09:17 AM ---------- Previous post was at 09:13 AM ----------
Am surw many know this still thought I'll post an observation as a note
"You have to extract the CSC from cache.img and copy it to system folder to avoid the keyboard null error after flashing"
Sent from my GT-N7000 using xda premium

was waiting for this
Thanks a lot.

Nice to see you thanks mate
Sent from my GT-N7000 using Tapatalk 2

Awesome
I'm here at work, setting this up instead of working. Don't tell anyone...

Great.
Thanks:thumbup::thumbup:
Von meinen Project-ReVo Black Beast gesendet.

Nice I will try it as soon as possible

Heyyyy! Thx read all about the kitchen in another thread . Glad it is here . Time to cook.
Sent from a secure institution......

Great to see official NOTE support. :laugh: You're amazing dsixda...A HUGE Thanks from all the XDA members!! :good: :fingers-crossed:

Thank you!

Welcome Here, Master,
We had Pleasure using the Kitchen in S2, now I don't find the words !!!! :fingers-crossed:
THANKS A MILLION.

this is so cool...too bad i dont have my ubuntu now...and i dont like using cygwin.but this is good to know.. it exists:cyclops:

@not-i or anyone kind enough to answer, I am having some confusion here and can't find an answer after hours of searching. I am wanting to run the kitchen for a NANDROID of a backed up ODEXED LT5. I am having issues figuring out how to get preload included. is there something I am missing here?

asf58967 said:
@not-i or anyone kind enough to answer, I am having some confusion here and can't find an answer after hours of searching. I am wanting to run the kitchen for a NANDROID of a backed up ODEXED LT5. I am having issues figuring out how to get preload included. is there something I am missing here?
Click to expand...
Click to collapse
Easy way if you have a Nandroid is open archive of preload.ext.tar.a (coming from philz kernel backup) with 7zip and copy preload folder straight into Working Folder. All done and very quick

not-i said:
Easy way if you have a Nandroid is open archive of preload.ext.tar.a (coming from philz kernel backup) with 7zip and copy preload folder straight into Working Folder. All done and very quick
Click to expand...
Click to collapse
ok, so when I actually build the zip via the kitchen, it will include preload? or should I just manually make it using a preexisting n7000 zip

asf58967 said:
ok, so when I actually build the zip via the kitchen, it will include preload? or should I just manually make it using a preexisting n7000 zip
Click to expand...
Click to collapse
Copy the preload folder into working folder before you deodex or do any mods. Thats what I have done anyway. I would then cut all apks from prelaod/app and paste into system/app for the deodex. Then when that is done copy those back that you want in preload.
The program will create the zip for you when you build it. I have found I need to modify updater script 9 out of 10 times though for it to flash. If yoour having trouble let me know and I'll forward you a script that works.
Make sure when you go through the process that the rom zip also includes create_preload_symlinks script. It should put this in for you in the process though.

S5830i defconfig use cooperve_defconfig when building from source

Hi friends of XDA,
I think this might be helpfull for some of you trying to compile kernel from source for S5830i, for the first time.
If you are following the great tutorials to build your first kenrel like:
http://forum.xda-developers.com/showthread.php?t=1748297 from thewadegeek
The first thing taht will happen, is that you cant pull defconfig from /proc/config.gz for S5830i.
Why? There is no such file for your device in there.
Normally the next you will do, is go to the stock sources readme file. And will find out the defconfig is totoro_defconfig
You will compile the kernel with no errors, and you will feel very happy, until you flash your recently compiled kernel and see that you get stuck in the boot_logo screen.
Ok, dont panic, solution is very easy. Samsung readme file is a general readme.
Here is the quid of the question:
totoro_defconfig is not the correct defconfig for S5830i.
S5830i defconfig is bcm21553_cooperve_defconfig
You will find this defconfig in the sources, at:
common/arch/arm/configs folder
Hope this helped. If it helped dont doubt to press the thanks button, this will be very appreciated.
Thank you and sweet kernel development.

Samsung's readme file isn't general, they just took the Galaxy Y's readme (even the model says GT 5360).
What's stranger is that the CHN sources have the correct info.
Also, I didn't need to pull anything. I just used the default config:
Code:
export ARCH=arm
export CROSS_COMPILE=<path>
make bcm21553_cooperve_defconfig
make -j16

Hi GermainZ,
Thats right,never had a look at the CHN readme. I wonder why the other sources are uploaded looooollll strange Samsun guys.
Never the less, forgot to post the next in the original thread.
I recomend to have an original copy of bcm21553_cooperve_defconfig as when you start modifing it some options may fail and its recomended to have a fresh one to copy paste quicly.
Even more for my kernel i copy original file and rename it to nit_defconfig and give it a version number ej nit01_defconfig, its agood practice have latest working defconfig as you will be modifying the file a lot, btw nit is how i call my kernel as you all ready know, this comes from new innovative technologies the name of one of my companys i created recently
But good appreciation GermainZ is always my pleasure to talk with you
Sent from my GT-S5830i using xda app-developers app

Thanks for your tips bro! You had a significant part in booting my kernel. Will add u in credits

No problem hell_lock.
Thank you.
Sent from my GT-S5830i using xda app-developers app

[ROM][WIP][HELP][NOOB] Firefox OS (B2G) for Optimus 2X: need help packaging

Before everyone starts flaming me and trying to kill me for being such a noob, i would like to say that i'm a teen and a noob.
ANYWAYS, i got bored and decided to have a go at porting Firefox OS to the Optimus 2X. After figuring out how to make a flashable zip out of .img's, I tested a bit. Unfortunately ADB doesnt work and I don't know how to do live kernel debugging.
What works: Kernel
What doesn't work: everything else
Source code: http://github.com/JordanRulz
Download:
First Semi-working attempt: http://d-h.st/juX (not a flashable zip)
2nd attempt: link on http://jordanrulz.tk/ (flashable)
3rd attempt (current): http://d-h.st/0We(flashable)
Turn signature verification off before flashing
BUILD INSTRUCTIONS (still doesn't work, but for anyone who thinks they might have the answer, go right ahead)
1.
Code:
git clone http://github.com/JordanRulz/B2G.git
2.extract a cm9 rom to B2G/my_device_backup
3.cd to the B2G directory and
Code:
ANDROIDFS_DIR=my_device_backup ./config.sh p990
and wait for the code to download. This has a good chance of failing because repo and git are stupid.
4.
Code:
./build.sh
5.edit core/sysroot/init.rc so that it imports init.p990.rc
6.go to line 98 of build/core/Makefile and change the build fingerprint to something acceptable by the build system
7.go online and find a wpa_ctrl.h and put it in hardware/libhardware_legacy/wifi/libwpa_client/wpa_ctrl.h
8.copy libcamera.so and libwpa_client.so from a cm9-based rom to out/target/product/p990/obj/lib/
9.it should turn out boot,img, system.img, a system folder, userdata.img, a userdata folder, etc. with adaptations, you should be able to craft a flashable zip out of the folders.
Please hit donate if you feel my work is worth donating to.

Good effort bro!

Way to go buddy.... Expecting this Rom for our beloved Optimus 2x. (me too a noob cant help much)..
Thanks and wish u best of luck..

ahahaha, great work! bring to the old O2X a new system!

Interesting tread, I'll look at the files. Let's hope this will be a cooperative tread to make this

Ok. What i did similarly to my phone to get this up. First, use PowerISO and extract userdata.img and system.img. Once done, its just like system folder of android while userdata is just data folder for user's data. Obviously. And then, the boot.img goes to the same as a flashable rom zip root folder. So basically, they are the same as flashing cm. Just need to add another few commands for recovery.img so that the whole thing is flashed like cm10

nicholaschw said:
Ok. What i did similarly to my phone to get this up. First, use PowerISO and extract userdata.img and system.img. Once done, its just like system folder of android while userdata is just data folder for user's data. Obviously. And then, the boot.img goes to the same as a flashable rom zip root folder. So basically, they are the same as flashing cm. Just need to add another few commands for recovery.img so that the whole thing is flashed like cm10
Click to expand...
Click to collapse
doesn't work. "invalid image file"

i think probably you can pm any recognised dev's for help....if you post a thread here i dont think anybody will try to help....you can pm the dev's like tonyp, harsh, carburano or anyone and you can ask for help in packaging and later on continue with your development....just an idea....:good:

good stuff man., were not the flaming community of yester year

This is getting really frustrating, after restarting multiple times and over 10 failed attempts. I have forked all the repos to my github so that all that want to help are able to do so. http://github.com/JordanRulz

Hello everyone. It's for new bl or old bl? Thanks
Sent from my LG-P990 using xda app-developers app

I say it´s for the old BL, if i don´t read the updater-script inside completly wrong.

It's for old bl
Sent from my LG-P990 using xda app-developers app

build instructions (for a non-working build, but still useful for f*cking around) were added.

JordanRulz said:
build instructions (for a non-working build, but still useful for f*cking around) were added.
Click to expand...
Click to collapse
:good::good:

Don't know if you're going at it the right way but good luck, and you should contact another dev just to make sure at least that you're on the right path.

I'm trying to get help from several devs.
Sent from my LG Optimus 2x using xda app-developers app

JordanRulz said:
I'm trying to get help from several devs.
Sent from my LG Optimus 2x using xda app-developers app
Click to expand...
Click to collapse
I hope if you develop successful, it will have 1 for SU660 :victory:

http://jordanrulz.tk/ not open the sites, is a virus java drive, jordan you really noob report on f.b.i

alexcyb said:
http://jordanrulz.tk/ not open the sites, is a virus java drive, jordan you really noob
Click to expand...
Click to collapse
Its not a "virus java drive", its a hidden bitcoin miner. If u use a secure browser like Firefox, it will prompt you before running it.
Sent from my LG Optimus 2x using xda app-developers app