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!
Hi,
i'm trying to compile google sources version 4.0.4 with samsung sources from opensource samsung
From samsung sources i've only used the platform files. I've done all the steps that are in the platform readme:
How to build Mobule for Platform
- It is only for modules are needed to using Android build system.
- Please check its own install information under its folder for other module.
[Step to build]
1. Get android open source.
: version info - Android gingerbread 4.0.4
( Download site : source android)
2. Copy module that you want to build - to original android open source
If same module exist in android open source, you should replace it. (no overwrite)
# It is possible to build all modules at once.
3. Check module is in 'build\core\user_tags.mk'
If not, you should add your module name in it.
ex1) external\libjpega : Write "libjpega \" into "build\core\user_tags.mk"
ex2) external\libexifa : Write "libexifa \" into "build\core\user_tags.mk"
4. In case of 'external\bluetooth',
you should add following text in 'build\target\board\generic\BoardConfig.mk'
BOARD_HAVE_BLUETOOTH := true
BOARD_HAVE_BLUETOOTH_BCM := true
5. excute build command
./build.sh user
The command user was ./build.sh eng
Before running this command i've installer jdk 6 and follow the steps from android initializing
the ./build.sh eng run with success and after this i've run the make.
Some hours later i've got a new folder "OUT", inside there is a system folder but i've tryed to flash this folder with odin
and no success.
What am i doing wrong?
Thanks.
Trying to build the kernel + modules?
If i understand what your trying to do, Install new kernel and modules?
!!!!!Before you try this, do some research for your device and make sure this is the correct action!!!!!
you are looking for a file called: zImage
It should be in <build path>/arch/arm/boot/
To install the new kernel, you put your device into fastboot
Code: adb reboot-bootloader
Then you can install the new kernel:
Code: fastboot flash zimage /<path to your zImage file>/zImage
Then you can boot your device and manually copy over the modules.
Note: I didn't see in your steps where you mentioned configuring the kernel, are you doing this?
Thanks for your reply.
the kernel i've already compiled like you mentioned and it is ok i've flashed the zImage.
But there is another part that is the platform module that corresponds to the system.
When you have a Rom there are 3 things inside:
- boot.img that has the zImage (kernel)
- meta-inf
- system
i'm changing the code in one file that corresponds to the nfc part and them compile the samsung sources
and google sources to get that system.
after compile the is one folder out that has system.img but i can't flash this .img file the mobile phone gets like a stone :S
All Black!
Please describe the process you are using to flash the system.img.
Have you though about just copying over the modified files?
Also, if you could create a step by step list of your process, maybe we can figure out what's going wrong.
i've compiled the google+samsung sources and this created the system.img.
Then i used Heimdall to choose only system to flash and It didn't work.
i've tryed also to change only the nfc.apk file put it in the app folder tryed to flash the ROM (in this case from Cyanogenmod) and it didn't work.
Thanks.
pec0 said:
i've compiled the google+samsung sources and this created the system.img.
Then i used Heimdall to choose only system to flash and It didn't work.
i've tryed also to change only the nfc.apk file put it in the app folder tryed to flash the ROM (in this case from Cyanogenmod) and it didn't work.
Thanks.
Click to expand...
Click to collapse
have you tried to remove and install your nfc.apk using adb rather than trying to flash the entire rom? I would think all you need to do is mod the kernel, flash the kernel, then copy over any modules and replace the nfc.apk.
Hello guys,
I have a samsung galaxy ace plus gt-s7500W and i read about:
[GUIDE][REL][YOU MUST KNOW][DL] Galaxy Ace Plus Frameworks And Kinds in the forum.
I went to the opensourse site of samsung and i downloaded the opensource rom but i don't know how to build and make it ready for flashing.
The file name is: GT-S7500W_GB_Opensource.zip
It contains two files:
GT-S7500W_EUR_Kernel.tar.gz and GT-S7500W_EUR_Platform.tar.gz
and also two text files:
GT-S7500W_EUR_Kernel.txt which contains this text:
Code:
HOW TO BUILD KERNEL 2.6.38 FOR GT-S7500
1. How to Build
- get Toolchain
Visit http://www.codesourcery.com/, download and install Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI.
Extract kernel source and move into the top directory.
$ toolchain\arm-eabi-4.4.3
$ cd kernel/
$ ./make_kernel_GT-S7500.sh
2. Output files
- Kernel : kernel/arch/arm/boot/zImage
3. How to make .tar binary for downloading into target.
- change current directory to kernel/arch/arm/boot
- type following command
$ tar cvf GT-S7500_Kernel_Gingerbread.tar zImage
and another file GT-S7500W_EUR_Platform.txt containing following text:
Code:
How to build
1. Get android open source.
: version info - Android gingerbread 2.3.6
( Download site : http://source.android.com )
2. Overwrite modules that you want to build.
3. external/bluetooth : Delete this source tree at Android gingerbread and then copy.
external/iproute2 : Delete this source tree at Android gingerbread and then copy.
4. Add the following lines at the end of build/target/board/generic/BoardConfig.mk
BOARD_HAVE_BLUETOOTH := true
BOARD_HAVE_BLUETOOTH_BCM := true
5. Write the following lines into build/core/user_tags.mk so that add these modules.
gatttool \
qcm_dut \
ip \
6. make
- ./build.sh user
How can i do that? :angel:
help me please
Hi,
I'm currently trying to build a kernel for my GT-P5110. I have a stock Android 4.2.2 which I downloaded from sammobile. I also downloaded the kernel from Samsung Open Source. I've use split_bootimg.pl to get the ramdisk from the boot.img and mkbootimg to make a boot.img from my zImage build successfully and the ramdisk. The problem is, when I flash my boot.img, I get stuck on the Samsung Galaxy Tab 2 logo even if I use the android_espresso10_omap4430_r02_user_defconfig which is suggested by Samsung.
Is there anyone able to sucessfully flash this kernel on his device?
Update: It seems like the defconfig file included in the Samsung Open Source contains some error.
If you want a working defconfig file use this one: http://forum.xda-developers.com/showpost.php?p=37685672&postcount=12
Hi all,
I'm following the guide at CM wiki to build for samsung n7100:
**tp://wiki.cyanogenmod.org/w/Build_for_n7100 (sorry)
While executing device/samsung/n7100/extract-files.sh, I note that some files are missing from my device (running CM version 11-20140505-SNAPSHOT-M6-n7100):
Code:
/system/bin/bcm4334_semco.hcd
/system/bin/lpm
/system/lib/libaudiosa.so
/system/vendor/lib/liblvverx.so
/system/vendor/lib/liblvvetx.so
/system/vendor/lib/mediadrm/libwvdrmengine.so
The build fails with make complaining about no rules to make these files.
What makes me confused is that the stock system.img does not contain these files either. So why are they listed as dependencies, or why does the script try to extract them? How can I carry out a successful build?