Hello,
since I don't yet have access for the specific section I post here
I can't find how to flash a kernel built from source (aka zImage). Since fastboot is not available on GS3, I just want an alternative tech to boot my gs3 with my build zImage.
I build the source from stock kernel samsung opensource database (update 8) and receive a zImage file.
I made a backup with cwm and unpack the boot.img with a perl script, then repack a new boot.img with my zImage as kernel and the ramdick from unpack but cannot boot with new package.
Could someone maybe give me a kernel source and the right corresponding package to boot it. Or maybe just a good way to make the whole process.
My final goal is to build a custom module for the GS3, that's my I need building from source and not an already-packed-kernel. Moreover if someone can help me directly about the module, he's very welcome
Related
Hello To All
This no longer when I managed to start kernel development.I used this source for compiling (my device is Gio).This is a custom kernel with cf-root and this is for GB roms.Used 2009q3 toolchain for compiling.I have went to the source dir and typed this:
make gio_defconfig
and configs done(i used config which was in the source not taken from another kernel).Then i typed to compile.when the compiling completed repacked zimage and its modules with a cm7 ramdisk kernel which was made by same dev(the person whom i got source from his githube)
when i flash the kernel it shows samsung logo then shows white screen (bootloop)
need devs help.I even tried a stock ramdisk but no result.
I need devs help.expect more
Hi,
I don't try to flood, just to increase my chance to have any help
I want to build a custom module for my GTi9300. Since the module need to be compiled whith the same kernel on the phone, i tried to build and flash a kernel from source (aka zImage). Since fastboot is not available on GS3, I just want an alternative tech to boot my gs3 with my built zImage.
I build the source from stock kernel samsung opensource database (update 8) and receive the zImage file.
I made a backup with cwm and unpack the boot.img with a perl script, then repack a new boot.img with my zImage as kernel and the ramdick from unpack but cannot boot with new package.
Could someone maybe give me a kernel source and the right corresponding package to boot it. Or maybe just a good way to make the whole process.
------------------------------------------------------------------------------------------------------------------------------
Moreover if someone can help me directly about the module, he's very welcome.
Without having the same kernel on the phone, I already tried to insmod my module. I've got first some version error, with the module_layout. Even if I correct it the module still doesn't load. In the kernel source, I modify the Subversion in the kernel to match with the one on the phone. But the compilation result add a "-gc33f1bc-dirty" to the end. Maybe I miss something to do before the compilation
Please post all questions in the Q&A section.
Thread Moved and Closed as you already have a thread going for this over there.
Hi everyone,
I need some help while I try to compile my first kernel (for experiments) with the Linaro-Toolchain. I followed a youtube instruction and it works well till the point to handle a stock/original boot.img file (with $ abootimg -x boot.img)
INFO: I´m playing with the slimkernel source, Linaro toolchain and mint 17.
Well before bothering you, i tried 1000 different ways to get this boot.img. But:
- extracted stock fimware only contains a boot.bin (and size does not match)
- a boot.img form a custom kernel zip brings me "no Android Magic value. giving up"
- downloadable boot.img are for all other phones excluding i9100...
Do you have any idea how to get this f****g boot.img which is working to get the kernel compiled, or do you know what i did wrong with that??
Thanks in advance
Ambador
Have you tried to extract a boot.img from a slimrom zip?
Yes I did but gave me the same result. I tried different kernels, roms and everytime while typing abootimg x -boot.img the fail appears.
Ambador said:
Yes I did but gave me the same result. I tried different kernels, roms and everytime while typing abootimg x -boot.img the fail appears.
Click to expand...
Click to collapse
I don't know really what you are doing atm because you are compiling a kernel from the kernel sourcecode. But I think that you are going to replace the zImage in the boot.img because kernel compiling doesn't include ramdisk right? Did you ever tryed to use dsixda-kitchen, It's usefull and also easy to use with kernel extracting.
Sorry if I got you wrong.
I used that kitchen already, but gave me the same missing android magic issue.
I tried an other thing, cuz im currently using apolo 7.1 kernel:
this kernel has a zimage only. So is it a possible way to get the kernel source, make a change (add an scheduler which is not in kernel) to see if it will work, compile the zimage with linaro and just replace it in the kernel.zip??
I AM NOT RESPONSIBLE IF YOUR PHONE DIES DUE TO THIS
I have successfully created a custom kernel for the Samsung Z2! This is built from source using the linaro 4.9 gcc toolchain here: https://github.com/ne0z/tizen_toolchain_kernel
This will only work on the Samsung Z2, not any other tizen phone.
This has only been tested on the Z200F. I have not tried any other variant, but it should work.
In my testing, there hasn't been any difference in performance.
It is a "dirty" kernel because it is not officially signed by Samsung
This kernel is an upstreamed kernel, meaning that it has been updated to linux kernel 3.10.106. There are no other edits besides that.
Attached you will find the tar file which contains two files. dzimage and modules.img. You require both of them to boot the kernel. This is because Tizen does not use a boot.img or a recovery.img.
To flash the kernel, use either lthor or ODIN. ODIN is recommended. If you don't know what lthor is, it isn't for you.
Steps:
1) Boot your Z2 into Download mode
2) Load the tar file into ODIN in AP
3) Flash
4) Profit
To verify that you have the new kernel running properly, download AIDA64 from the tizen store and open the "Tizen" option. Scroll down to kernel version and you should see the new kernel version say "3.10.106-dirty"
Enjoy!
Source (use branch "edit"): https://github.com/Qiangong2/stock_kernel_3.10.65_sc9830_samsung
Hello everyone.
I'm trying to compile from source the kernel of my phone which is an unlocked motorola g6 play codename aljeter with the stock rom (android pie). I found the kernel repository in this post https://forum.xda-developers.com/t/rom-r-v5-unofficial-aljeter-bananadroid-for-moto-g6-play.4362405/. I downloaded the toolchain in my case arm-linux-androideabi-4.9 because my phone architecture is arm.
Then i extracted the defconfig from the stock kernel obtained from the extraction of stock boot.img using AIK. After that i successfully compiled the kernel and i obtained the Image, zImage, and zImage-dtb. I unpacked the boot.img using AIK and i changed the boot.img-kernel with my zImage-dtb (and of course i renamed my zImage-dtb with boot.img-kernel). Then i repacked everything and i obtained a image-new.img. I rebooted my phone in fastboot mode and i run "fastboot boot image-new.img" to boot the new boot.img. After that the phone showed the boot logo but it immediately reboot to the stock boot.img (stock kernel). I think that the problem is related to avb but i am not sure.
Does anyone know how can i fix that?
Thanks
P.S
I also tried to compile the kernel for my tablet which is a Lenovo X606F but i obtained the same error