So I have a phone that doesn't have a kernel source, instead it has a Zimage. And sadly my dumbass can't really comprehend how to create a kernel source from zimage. Plus, even if I can, it's probably wayyy out of my league. Anyways, I was wondering if I would be able to compile a kernel without source. Plus if I create a kernel for my phone, could I use that kernel source to build other stuff too.
Zimage is kernel it is enough to make your own TWRP for your device ...
ineedroot69 said:
Zimage is kernel it is enough to make your own TWRP for your device ...
Click to expand...
Click to collapse
Yea I already compiled a twrp for my device. I want to modify the ramdisk and make the battery last longer... maybe learn how to overclock.
Related
P6200: https://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-P6200
P6210: https://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-P6210
any more info? i am assuming that this cannot compile to a fully working rom? there must be missing binary blobs? perhaps this is just kernel source? anything else you can tell me would be awesome thank you!
SGH-T869: https://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SGH-T869
The zip files each contain two tarballs. One for kernel source and the other for platform stuff.
The kernel stuff is semi-complete... it'll compile a proper kernel, but won't be bootable on your device unless you add an initramfs image. You'll also need to pull the proprietary loadable modules from your device and embed them in that same initramfs. There's enough there that with some know-how and tools you can create a new kernel image...
The platform stuff... well, I haven't messed with that. I honestly don't know what is in there that isn't already in the AOSP. I do know that it doesn't contain things like touchwiz...
Take care
Gary
this is great news! i juat recently got a good build platform put together on an old laptop so this will be fun to take a crack at!
garyd9 said:
The zip files each contain two tarballs. One for kernel source and the other for platform stuff.
The kernel stuff is semi-complete... it'll compile a proper kernel, but won't be bootable on your device unless you add an initramfs image. You'll also need to pull the proprietary loadable modules from your device and embed them in that same initramfs. There's enough there that with some know-how and tools you can create a new kernel image...
The platform stuff... well, I haven't messed with that. I honestly don't know what is in there that isn't already in the AOSP. I do know that it doesn't contain things like touchwiz...
Take care
Gary
Click to expand...
Click to collapse
Are there any proprietary kernel modules? There aren't for other Exynos devices (GSII, Galaxy Note).
Original GalaxyS had some (FSR/RFS, also j4fs - j4fs is open-source on Exynos devices)
Entropy512 said:
Are there any proprietary kernel modules? There aren't for other Exynos devices (GSII, Galaxy Note).
Click to expand...
Click to collapse
Well... I thought there were. I know there were modules on my 6210 /lib/modules that didn't get built from the kernel. I don't remember right now which ones, though. (I'm at work...)
Take care
Gary
garyd9 said:
Well... I thought there were. I know there were modules on my 6210 /lib/modules that didn't get built from the kernel. I don't remember right now which ones, though.
Click to expand...
Click to collapse
Okay, you were correct. For the GTP6210, only one module from the factory recovery (and main boot) which isn't being built by the kernel build:
j4fs.ko (as you already mentioned.)
Take care
Gary
garyd9 said:
Okay, you were correct. For the GTP6210, only one module from the factory recovery (and main boot) which isn't being built by the kernel build:
j4fs.ko (as you already mentioned.)
Take care
Gary
Click to expand...
Click to collapse
Odd... On Exynos devices, j4fs should be getting built...
https://github.com/Entropy512/linux_kernel_sgh-i777/tree/master/drivers/samsung/j4fs
Its odd location for an FS driver (in drivers/staging/samsung) puts it in a weird location in menuconfig too.
j4fs is used to access param.lfs
There also seems to be missing a "ar6000" device, but it's not in /lib/modules on the factory initramfs either. Of all things, it's in /system/wifi. (and there's no source.)
if I recompile the kernel sources from samsung's website (doing everything properly, of course), it won't load that module... claims a version mismatch (and won't allow me to override.)
Here's the uname string from the factory normal boot (KL1) kernel:
Code:
Linux localhost 2.6.36-P6210UEKL1-CL583281 #3 SMP PREEMPT Fri Dec 2 21:14:23 KST 2011 armv7l GNU/Linux
The kernels I recompile have a slightly different string:
Code:
Linux localhost 2.6.36 #4 SMP PREEMPT Sat Dec 10 23:40:09 EST 2011 armv7l GNU/Linux
I guess that makes the kernel source a bit less useful. Perhaps after they drop the KL1 updated kernel sources I'll be in better shape.
Yet, I can't help but to feel like I missing something obvious... Just can't remember what. perhaps after a good night sleep it'll come to me.
edit: found a source for the ar6000 code (http://nv-tegra.nvidia.com/gitweb/?p=3rdparty/atheros.git) I'll play with it more tomorrow or over the weekend.
Take care
Gary
Would anyone know how to go about getting the drivers for the IR port? I have an early version of the 7.7 that has the IR blaster but the Peel app is saying it's not present. I think I just need to flash the drivers for it, but I'm rather ignorant of this. Any ideas?
Hi I looked for sometime for answers but could not find anything relevant.
Looking to get the ftdi VCP drivers to install on Xoom. Which means I either have to compile a kernel or add them as a module. I can not for the life of me find the correct source tree.
I downloaded kernel 2.6.36.3 from google which matches my kernel version.
My kernel version on the tablet is 2.6.36.3-gb899258 .
When I cross compile the module and try to do an insmod its complaining about the magic version is different which leads me to believe that I have the wrong kernel.
Where can I get the right stock kernel?
If i can not find it there is another option to download the config.gz from the device and recompile another version of the kernel with native support for the ftdi drivers.. How do i just install just the kernel on the device? Is it a uImage bzImage and how do I just flash that?
cd
Thanks
edit:
scrap that ...
sorry, not really helpful in your case
I'm assuming you got your source from here? This is the link from the Android website:
git clone https://android.googlesource.com/kernel/tegra.git
If you decide to go the route of compiling another kernel source, the easiest way (and a good way to keep snapshots of various configs) would be to use Koush's AnyKernel to flash the kernel. I don't know anything about what you're trying to do but I hope that helps some.
Yep the code comes from there.....
I finally got it to work , I downloaded the stock kernel from google then when I make the modules I had to modify the Makefile to get it to match the kernel versions.
It seems to work for now...
Thanks for your help
Haii guys!
So, i'm young "kernel developer".. I am actually not a coder, i just try to learn by making kernels and if they are stable enough i test them. So, till now i was working with Mako source - i had phone lg optimus g which i really close to mako and i based everything on Mako source.
Now i bought a new phone, Nexus 5. I am really satisfied by this phone on stock, but even more on custom ROM & Kernel.. But hey, it's me, i'm curious and i have to try to make stuff myself, so i choose to make my own kernel for Nexus 5.. More to learn than anything.
So, i started.. I forked this to my github and do some basic changes for me.. Just to start. I added graphite support and option to build with Linaro 4.9.4.. And i started to build. And it had some errors, so i also fixed them - fs/namespace.c error with 4.9 toolchains, so, i fixed it and it built with no trouble.
So, i was coming from world of Mako and took zImage, made a flashable zip with AnyKernel and flashed it.. And i was stuck at google logo with unlock icon. I restored twrp backup of previous kernel and started over and it booted normally...
Then i did some research and found out that i should use zImage-dtb because Nexus 5 uses something named device tree blob.. So, i did everything from scratch.
I forked same source as before, and did my changes over it.. Renamed kernel, added kernel build script, made my slightly modified defconfig, this time i used toolchain LinaroMod 4.9 from here and some other stuff.. I built with no trouble, used zImage-dtb as zImage in flashable zip as i saw in other kernels and flashed.. I was sure it will boot this time, none of those modifications was supposed to break anything.. But again, I am stuck at Google logo.
Have any of you guys any idea where i missed? Maybe wrong source? Wrong toolchain?
Here are some maybe useful links:
My source: https://github.com/Matthew-333/BlueMoon
My Changes: https://github.com/Matthew-333/BlueMoon/commits/master
Toolchain: https://github.com/hyper-toolchains/LinaroMod-arm-eabi-4.9
AnyKernel Template: https://github.com/koush/AnyKernel
I am using xUbuntu 15.04 64 bit..
Thank you if anybody manage to help me with this...
Matthew_333 said:
Haii guys!
So, i'm young "kernel developer".. I am actually not a coder, i just try to learn by making kernels and if they are stable enough i test them. So, till now i was working with Mako source - i had phone lg optimus g which i really close to mako and i based everything on Mako source.
Now i bought a new phone, Nexus 5. I am really satisfied by this phone on stock, but even more on custom ROM & Kernel.. But hey, it's me, i'm curious and i have to try to make stuff myself, so i choose to make my own kernel for Nexus 5.. More to learn than anything.
So, i started.. I forked this to my github and do some basic changes for me.. Just to start. I added graphite support and option to build with Linaro 4.9.4.. And i started to build. And it had some errors, so i also fixed them - fs/namespace.c error with 4.9 toolchains, so, i fixed it and it built with no trouble.
So, i was coming from world of Mako and took zImage, made a flashable zip with AnyKernel and flashed it.. And i was stuck at google logo with unlock icon. I restored twrp backup of previous kernel and started over and it booted normally...
Then i did some research and found out that i should use zImage-dtb because Nexus 5 uses something named device tree blob.. So, i did everything from scratch.
I forked same source as before, and did my changes over it.. Renamed kernel, added kernel build script, made my slightly modified defconfig, this time i used toolchain LinaroMod 4.9 from here and some other stuff.. I built with no trouble, used zImage-dtb as zImage in flashable zip as i saw in other kernels and flashed.. I was sure it will boot this time, none of those modifications was supposed to break anything.. But again, I am stuck at Google logo.
Have any of you guys any idea where i missed? Maybe wrong source? Wrong toolchain?
Here are some maybe useful links:
My source: https://github.com/Matthew-333/BlueMoon
My Changes: https://github.com/Matthew-333/BlueMoon/commits/master
Toolchain: https://github.com/hyper-toolchains/LinaroMod-arm-eabi-4.9
AnyKernel Template: https://github.com/koush/AnyKernel
I am using xUbuntu 15.04 64 bit..
Thank you if anybody manage to help me with this...
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
Please have a look here for some useful information:
http://forum.xda-developers.com/android/software/ultimate-guide-compile-android-kernel-t2871276
Good luck!
Hello Everyone, how are you?
I've started the path of "android compilation", well right now I just succesfully compiled TWRP for one of my devices
But I have some questions for you all...
First of all, is it possible to compile a rom without compile the kernel? (like when you compile a recovery)
Second, how can I extract blobs from my stock rom and how can I know what file to pick?
Third, if I want to compile a rom from source for my device (without device tree and having only stock kernel), what are the needed configurations to make in BoardConfig.mk?
Sorry for those questions, but I want to learn and a lot of informations are missing around the web (for example, someone says that it's possible to compile a rom without kernel source, someone say that it's impossible)
Hi all,
Im trying to flash a custom built kernel on a g930fd device running android 6.0.1.
ive did the following steps:
built the kernel - the source matches with the rom on the device
replaced the out Image using AIK
created a flashable zip and tried to instal it via TWRP.
another steps ive tried as sanity checks, ALL RESULTED IN BOOT ANIMATION LOOP:
1. dd out the boot.img form running device, dd that boot.img back to /dev/block/platform/*/*/BOOT
2. flash boot.img with odin
3. built dtb and Image and flashed in using Lazyflasher
IF SOMEONE KNOWS WHAT COULD BE THE PROBLEM, ILL APPRECIATE ANY HELP , THANK YOU.
@osm0sis i hope maybe you can help me with a valuble input thanks in advance!
Where's your source?
djb77 said:
Where's your source?
Click to expand...
Click to collapse
i got it from samsung opensource
qroot0 said:
i got it from samsung opensource
Click to expand...
Click to collapse
You do realise you still have to modify it in order to get it to work properly.
So where is YOUR source code? What's your github link?
djb77 said:
You do realise you still have to modify it in order to get it to work properly.
So where is YOUR source code? What's your github link?
Click to expand...
Click to collapse
Sorry,
heres the link:
github.com/IgalGokhman/8890-6.0.1-custom-kernel
Ive reverted the changes i made to the defconfig.
BTW, Its my first time building a kernel for samsung device, so im not sure about all the chhanges i need to make in order to run it on the device.
Ive read a lot through xda and othher forums but the majority of them just saying: run make and install using updater-script...
qroot0 said:
Sorry,
heres the link:
github.com/IgalGokhman/8890-6.0.1-custom-kernel
Ive reverted the changes i made to the defconfig.
BTW, Its my first time building a kernel for samsung device, so im not sure about all the chhanges i need to make in order to run it on the device.
Ive read a lot through xda and othher forums but the majority of them just saying: run make and install using updater-script...
Click to expand...
Click to collapse
Well, I really needed to see what changes you made to start with, because all I have in front of me now is clean source.
Most of us use a build.sh script of some sort which builds the zimage, dtb, and ramdisk. My script does it all, builds kernel and zip.
Here's my old MM kernel that you can have a look at:
https://github.com/TheGalaxyProject/tgpkernel-s7-mm
If you use any of this please give credit
djb77 said:
Well, I really needed to see what changes you made to start with, because all I have in front of me now is clean source.
Most of us use a build.sh script of some sort which builds the zimage, dtb, and ramdisk. My script does it all, builds kernel and zip.
Here's my old MM kernel that you can have a look at:
https://github.com/TheGalaxyProject/tgpkernel-s7-mm
If you use any of this please give credit
Click to expand...
Click to collapse
Thanks I’ll take a look.
I do have a build script, eventually I have an Image and a dtb.image, from both of them I make a boot.img with AIK.
I tried to build the kernel with the config values I pulled from the device /proc/config.gz and with the “as is” values in the arch/arm64/configs/exynos_8890_defconfig
Both boot.imgs bootlooped the device