Hello,
First of all, this is my first post in the forum and my first time trying to compile an Android kernel.
My intention was to port Nethunter for my tablet, Samsung SM-T580 (Galaxy Tab A6 10.1 only wifi).
I have successfully compiled the original kernel offered by samsung and i have ended up with a file called Image, a file called Image.gz and a dts folder
I have extracted the original rom boot.img with mkbootimg_tools and i see a kernel file, a ramdisk folder, a ramdisk.packed file and a dt.img
For what i have found is that this must be a non standard thing, the way samsung manages this, and despite i have seen various guides on compiling samsung kernels, i haven't found anyone doing it straight from samsung sources.
I think that the dt.img part is solved with the dtbTool, but i haven't been able to figure out what to do with Image and Image.gz to get the kernel and ramdisk.
¿Can someone give me a lead on this? ¿Is it doable? ¿Should i look for other kernel instead?
Its been long time ago... But did you manage to compile the kernel?
Related
i own samsung galaxy pocket gt-s5300, its like galaxy Y little brother. And i'm trying to build from source.
i'm new in this stuff, so i can't elaborate enough to find solution myself.
i've downloaded the samsung source for this device from samsung website, when extracted it has 2 sources, platform and kernel.
im trying to build the platform and hopefully can build the stock rom successfully so i can proceed to modification.
already followed the instructions to get the gingerbread 2.3.6 from aosp, merge the folders from samsung to aosp, and execute build script (generic-user). seems fine, i got system.img,userdata.img,etc but no boot.img, still tried to flash anyway and figured that this device doesn't support fastboot but adb works. then i tried to make otapackage but got no rule error. perhaps caused by this generic-user lunch, but i dont know how to add this device to build, because there's only generic,emulator,crespo-4g, and crespo choices.
trying to find alternatives, and thinking about modify the stock rom with my build, so i also tried to open the odin flashable stock rom with winrar (xxx.tar.md5) which i cant, i dont know why since the other galaxy rom has no problem.
so many thing i'm not sure of doing it right, so i need help building for this samsung device from source.
bLusiLv said:
i own samsung galaxy pocket gt-s5300, its like galaxy Y little brother. And i'm trying to build from source.
i'm new in this stuff, so i can't elaborate enough to find solution myself.
i've downloaded the samsung source for this device from samsung website, when extracted it has 2 sources, platform and kernel.
im trying to build the platform and hopefully can build the stock rom successfully so i can proceed to modification.
already followed the instructions to get the gingerbread 2.3.6 from aosp, merge the folders from samsung to aosp, and execute build script (generic-user). seems fine, i got system.img,userdata.img,etc but no boot.img, still tried to flash anyway and figured that this device doesn't support fastboot but adb works. then i tried to make otapackage but got no rule error. perhaps caused by this generic-user lunch, but i dont know how to add this device to build, because there's only generic,emulator,crespo-4g, and crespo choices.
trying to find alternatives, and thinking about modify the stock rom with my build, so i also tried to open the odin flashable stock rom with winrar (xxx.tar.md5) which i cant, i dont know why since the other galaxy rom has no problem.
so many thing i'm not sure of doing it right, so i need help building for this samsung device from source.
Click to expand...
Click to collapse
I try to do it but i still make a lot of tweaks on my Rom I need to make good performance to my phone
I have Just one thing I can't figure out when porting a rom. Its the config for the kernel when I unpack it I know I am suppose to get the zimage and replace with the kernel I am porting to and rename the .rc files and replace lib files.But when i recompiile it and flash it to my device.It gets stuck on the android logo after rle image boot.Can someone please help me out since I seem to be the only one porting or making a roms for the samsung Repp sch-r680 at the moment. Also I can't seem to figure out how to overclock a kernel ether or find anything on google and believe me I search over like 50 google next results and nothing.I ant a totally Noob ether I have already made a custom rom for the repp with init.d support and found another way to root it using my clockwork mod that I ported over to it.I also added busy box and su to the cwm for adb support.
samsungcrasher said:
I have Just one thing I can't figure out when porting a rom. Its the config for the kernel when I unpack it I know I am suppose to get the zimage and replace with the kernel I am porting to and rename the .rc files and replace lib files.But when i recompiile it and flash it to my device.It gets stuck on the android logo after rle image boot.Can someone please help me out since I seem to be the only one porting or making a roms for the samsung Repp sch-r680 at the moment. Also I can't seem to figure out how to overclock a kernel ether or find anything on google and believe me I search over like 50 google next results and nothing.I ant a totally Noob ether I have already made a custom rom for the repp with init.d support and found another way to root it using my clockwork mod that I ported over to it.I also added busy box and su to the cwm for adb support.
Click to expand...
Click to collapse
I have a repp that I'm interested in working on. I've never ported a rom, but I understand Linux and some Android, and I don't mind staring at a terminal all day. I'd like to get something aosp working on it.
Let me know if you're still working on this phone.
Hi everyone, I am looking for a point in the right direction or any advice.
My device is Samsung Galaxy Note 3 SM-N9005. I know there is a forum for that device but I feel I need help from experienced kernel devs and I am unsure where to ask for help
I have downloaded the source files from Samsung for this device (it has kernel and platform archives).
I have a linux dev environment setup in virtual machine. I successfully compiled the kernel zImage. I managed to unpack the current boot.img and replace the zImage and repack and the phone boots. So that is a success for a first time hey?
However, WIFI does not work. I have read that I have to compile the wifi module for it, but I am clueless.
Do I, or don't I, need the Android 4.3 source code from Google?
Do I have to run "make menuconfig" and enable modules (currently not enabled)?
Do I have to somehow compile a wifi module?
Any help will be massively appreciated!!!
Thanks
Dan
I know this is a bit scarce, but I need help with a kernel. Why? Because I unfortunately don't have a
computer at the moment (much less Ubuntu suite), just my trusty GT-i9505. Also, I have a few
questions.
First of all, this is the guide I am following:
[GUIDE] Use aircrack-ng on android phone using Wireless USB Adapter
http://forum.xda-developers.com/showthread.php?t=2338179
This guide is aimed towards amateur kernel builders,
and the suggested ROM for use with this is Cyanogen Mod. Although, the post does mention that he was able to use his stock touchwiz ROM. He mentions he was able to do it with a few minor adjustments (along with the kernel and .md5 file):
I got this to work on my stock Samsung TouchWiz ROM by making a few adjustments:
- Get the kernel from Samsung: http://opensource.samsung.com/
- Change the lines in the .config file of the kernel below ## Samsung Rooting ... from =y to =n using nano
- To get boot.img, download the ...tar.md5 firmware matching your current firmware from http://www.sammobile.com/firmware/, rename .tar.md5 to .tar, and extract the boot.img. You cannot use mkbootimg here, only abootimg, as this boot.img has a special ramdisk address!
Click to expand...
Click to collapse
I would love to do this with my current TouchWiz ROM, (not stock) Samy Deluxe ROM- Operation Ivy
Any help/luck doing this? Thanks in advance
Bump
Bump. Let me also add that I can give the source to the kernel (of the ROM I have).
Really all that needs to be done is to rebuild that kernel (and follow the steps of course to the guide I'm using).
I have a TP Link tl-wn722n USB Wireless adapter, so I need to have the module/driver installed into that kernel.
The name of the kernel is 3.4.100-GoogyMax3_TW-v1.1.3
Here's the link to the kernel: http://forum.xda-developers.com/attachment.php?attachmentid=2895862&d=1407942420
I downloaded my kernel and looked inside of the zip file and don't seem to find a ".config" file as mentioned in the guide, but did see a boot.img so I don't believe there's a need to download the .md5 file:
I got this to work on my stock Samsung TouchWiz ROM by making a few adjustments:
- Get the kernel from Samsung: http://opensource.samsung.com/
- Change the lines in the .config file of the kernel below ## Samsung Rooting ... from =y to =n using nano
- To get boot.img, download the ...tar.md5 firmware matching your current firmware from http://www.sammobile.com/firmware/, rename .tar.md5 to .tar, and extract the boot.img. You cannot use mkbootimg here, only abootimg, as this boot.img has a special ramdisk address!
Click to expand...
Click to collapse
Any help at all would be greatly appreciated.
Bump... again...
I was trying to build Kernel from original HTC Source. My rom on phone has version 2.18.401.3, but the original HTC kernel source (enru-3.1.10-g7f360be.zip) with this version did not build, because it contains only hox (endeavour) "in arch\arm\mach-tegra" not HOX+ (enrc2b). I was using the extracted config from my device. The HTC kernel source with the biggest number (2.18.1136.2, enrc2b-3.1.10-42105bd.zip) builds properly but the merged boot.img did not boot. I checked with other boot.img from HOX+ i.e. from cyanogenmod (unpack, repack) whether I generate a correct one, but it was binary same. So I believe the zImage has some defect. Please help.
Trivalik said:
I was trying to build Kernel from original HTC Source. My rom on phone has version 2.18.401.3, but the original HTC kernel source (enru-3.1.10-g7f360be.zip) with this version did not build, because it contains only hox (endeavour) "in arch\arm\mach-tegra" not HOX+ (enrc2b). I was using the extracted config from my device. The HTC kernel source with the biggest number (2.18.1136.2, enrc2b-3.1.10-42105bd.zip) builds properly but the merged boot.img did not boot. I checked with other boot.img from HOX+ i.e. from cyanogenmod (unpack, repack) whether I generate a correct one, but it was binary same. So I believe the zImage has some defect. Please help.
Click to expand...
Click to collapse
use this, I kept it in tact for this reason :
https://github.com/Lloir/htc_kernel_oxp/tree/master
It's the source straight from htc
you'll also need this commit https://github.com/Lloir/htc_kernel_oxp/commit/b3cade38f9d17682778ea767722d20b94696f6ae which has the defconfig unless you already have it.
Enjoy
Lloir said:
use this, I kept it in tact for this reason :
https://github.com/Lloir/htc_kernel_oxp/tree/master
It's the source straight from htc
you'll also need this commit https://github.com/Lloir/htc_kernel_oxp/commit/b3cade38f9d17682778ea767722d20b94696f6ae which has the defconfig unless you already have it.
Enjoy
Click to expand...
Click to collapse
I tried the master branch, but it make boot loop all the time. Another test would be, if you can provide me a boot.img what I can test.
I found the solution, is for me a little bit strange but it works. In case somebody can show me the big difference that I can understand the "why", whould be fine.
I used for build this toolchain: prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin stored: git clone --depth=1 https://android.googlesource.com/platform/prebuilt
before I was using arm-eabi-4.8/bin/ from master branch(not sure about git clone path)
There is now one point I did not understand, I build original source, why is then my SIM not working? (no question for pin), (Answer: Maybe are the orignal modules signed. After change the modules on /system/lib/modules/ it was working like before), because after flashing the android revolution boot.img, it was all working. Any ideas? (Answer: It is because they didn't change th zImage)