HI everyone i need your help to develop a kernel with adhoc support for gt s7270(logan)
I followed the instruction:
1) I downloaded the kernel from the repo in git hub
2) I do the modifications in broadcom wifi driver to support adhoc mode
3) I compiled the kernel for my device and now i have the zimage.
Now because i do not how to create a ramdisk image I take the zip of rom(cm11) and decompresed the boot.img and split into ramdisk and zimage.
Now i ovewrite the zimage, and i repack the boot img, all this I did with the application that I found in xda(https://forum.xda-developers.com/showthread.php?t=2319018)
Now when i flashed the zip that constains the new zimage i get a boot loop. Can you help me and tell what i did wrong?
Related
Hi, i'm trying to flash my custom kernel with CWM recovery. I've seen some zip to update TF's kernel that use a kernelblob but i didn't realized how to create this binary file.
I've compiled kernel from source code from AsusTek files (Eee Pad Kernel Code for Android 3.2 OS (V8.6.5.7)) and i have zImage and modules (.ko).
Someone know how can i pack this things to flash my kernel with CWM?
Coniglioz said:
Hi, i'm trying to flash my custom kernel with CWM recovery. I've seen some zip to update TF's kernel that use a kernelblob but i didn't realized how to create this binary file.
I've compiled kernel from source code from AsusTek files (Eee Pad Kernel Code for Android 3.2 OS (V8.6.5.7)) and i have zImage and modules (.ko).
Someone know how can i pack this things to flash my kernel with CWM?
Click to expand...
Click to collapse
Just to create a CWM compatible kernel zip , it's a combination of the things below:
1) Fetch one of the many kernel zip files like from Roach or Clemsyn that are in the development forum to use as a template. Unzip it somewhere in a clean folder and you'll just be replacing modules & zImage (or whatever it is called, almost certainly *blob* something) then next step.
2) Most of what you need to create the insecure boot image is in here:
http://forum.xda-developers.com/showthread.php?t=1193737
3) Most of what you need to create the new blob is in here:
http://forum.xda-developers.com/showthread.php?t=1068548&highlight=blobpack
4) Now move your new modules from your freshly built custom kernel (do a $find {kerneldir} -iname '*.ko' ). Copy them over /system/lib/modules/* in the unzipped template zip from 1) and get rid of any that you didn't create yourself as well.
4.5) copy the blobpack'd file you created from zImage to whatever it was called in the unzipped zip template (say, boot.img to blob or kernelblob or whatever it was called so the script in the zip works).
5) zip the entire contents making sure you're starting at the right base directory into a new customized zip file. That's it you're done. If it doesn't work you might just have created a bum kernel.
Theory of this in a nutshell. There is no way to do the anykernel.zip method because the tf101 will only accept a blob on those encoded partitions so you have to get the blob and boot tools and use them and since all of the kernel zipfiles use it, you've got easy templates.
I'm not mentioning CWM in here because you would just have to create a bigger blob which is I think covered in any thread you search out that has 'blobpack' in it, like Rayman's. The catch-22 of doing recovery + kernel in one blob is that you have no way to boot the thing should things go haywire, unless you're just talking about CWM and it's kernel.
Good luck -
Hashi
Thanks, I blobbed my custom zImage.
I used this zip update as template: http://forum.xda-developers.com/showthread.php?t=1226717
I'll post this kernel with raw hid input support after testing all the functionalities!
Hello everyone,
I am newbie Android ROM development. Nowadays I try to port a specific custom ROM(a special ROM for my company) for Galaxy Tab2 10.1 (GT-P5100). But there is a point that I cannot figure out.
First of all I downloaded android ICS source code and apply my company's module patch to this source. Then I found device and vendor tree for my GT-5100 device and put it my source tree. Finally I built Samsung GT-P5100 kernel and put output file to correct place. At the end of these operations, I compiled all device tree successfully, now I have out/target/product/p5100 file which contains boot.img, system.img, userdata.img etc.(I attached an image file). Everything is fine untill this point. Normally in fastboot mode, I use "fastboot flashall -w" command and img files are automatically flashed to device. But GT-P5100 does not support fastboot mode.Question is this: How can I flash these img files(out/target/product/p5100 file) to the device? I searched lots of threads but cannot find a solution. I also tried to create a ROM which includes system file, boot.img and META-INF file. However it is not worked. Because create a META-INF file is very complicated and I have to find a quick flash option.
I need your helps.
Thanks,
------------------------------------------------------
Edit:
Finally I found solution. Just nedded to use command : make -j4 otapackage and then I get the ROM package to flash this AOSP.
Dear xda-developers members,
I need some help in the right direction:
I have installed Dhollmen's kernel (from forum.xda-developers.com/showthread.php?t=2176563) on my GT-P5110
which is rooted and running CM10.1 at the moment and I used cwm to flash the kernel (from the link above).
Now I am trying to compile the same Dhollmen's kernel from their source code (see link) and flash the compiled kernel.
This has not been a success yet. I either get stuck at bootscreen or in a boot loop.
What I have tried:
Code:
export ARCH=arm
export CROSS_COMPILE=~/android/toolchains/arm-eabi-4.4.3/bin/arm-eabi-
make dhollmen_P51XX_defconfig
make
This resulted in zImage file and I tried to flash with heimdall:
Code:
heimdall flash --KERNEL arch/arm/boot/zImage
This got me stuck on the bootscreen
Try 2:
With the compiled zImage and the working Dhollmen kernel zip (DhollmenCM-P51xx-Kernel_20130706.zip from the link)
I unpacked the working Dhollmen kernel, split boot.img, replace zImage with mine, repack to boot.img, repack to zip and flash zip from cmw
This got me stuck in a boot loop
The frustrating thing is that I have no errors so I am clueless of what is going wrong.
Can someone explain how you'd go from the source code (https://github.com/Dhollmen/DhollmenCM_kernel) to a flashable zip file?
Hi, I'm working on a custom kernel and I'm new on xda
So my problem here is from the repack scripts : bgcngm/mtk-tools on github
I'm doing :
unpack-MT65xx.pl boot.img
I do no changes on ramdisk or kernel.img and immediatly invoke
repack-MT65xx.pl -boot boot.img-kernel.img boot.img-ramdisk ../boot.img
But this gives me 2 differents sizes files (2 ko the difference between the original boot.img and the newboot.img) and the repacked boot.img won't boot.
So I'm doing something wrong but what ?
Hey folks,
I have rooted (magisk) OnePlus 8 phone with Android 11, w/o TWRP recovery. I'm trying to replace kernel with one of blue_spark, here's what I'm doing
1. Download zip file from https://github.com/engstk/op8/releases/tag/r112
2. Extract and unpack Image.gz
3. Unpack Magisk patched boot.img to /tmp (magiskboot unpack boot.img)
4. Replace kernel with unpacked Image (cp Image /tmp/kernel)
5. Repack boot.img (magiskboot repack boot.img boot-new.img)
6. Boot with boot-new.img (fastboot boot boot-new.img)
And here is when I'm getting into "QUALCOMM CrashDump Mode"
The same result if I build kernel from sources. Repacking boot.img with original kernel works, so problem is unlikely in magiskboot.
I'm trying to figure out the problem, but without kernel logs it's troublesome. Any ideas?
Thanks.
Hm... It looks like, I also have to update DTB. After that device boots successfully. Seems a bit strange to me. What's the difference in supported devices between blu_spark and stock kernel?
Ok, turned out AVB was enabled in the original device tree:
fsmgr_flags = "wait,slotselect,avb";
Switching it off fixes boot process.