[Q] How to pack zImage binary kernel in CWM zip for TF101 - Eee Pad Transformer Q&A, Help & Troubleshooting

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!

Related

[Q] Flash A Custom ROM : P3100 : Specific Issue - Fastboot Not Supported

I have made a custom ROM, with additional API's and patches using stock ICS source - Downloaded from source.android.com.
After modifying, patching etc, I built the ROM using 'make' on my Ubuntu machine.
I followed the steps here to build the ROM: http://source.android.com/source/building.html
The output of this procedure is attached as a screenshot
(I copied the folder to windows hence the screenshot shows a windows OS)
Now I have a ROM I am asked to flash it using'fastboot flashall' per the instruction here:
http://source.android.com/source/building-devices.html
My device doesn't seem to support a Fastboot mode.
The output folder of the ROM is attached as a screenshot.
A> When I try to use CWM, it fails to flash - MD5 Mismatch:
Also I am unsure how CWM flashes and which of the folders are to be included. A CWM recovery generates:
1. boot.img
2. recovery.img
3. system.ext4.tar
4. data.ext4.tar
5. cache.ext4.tar
6. nandroid.md5
Clearly my output folder is not aligned to this format. So I'm a bit lost here.
B> Odin takes on tar file. I am not sure if simply making the folder a tar will work.
C> Heimdall doesnt support this tab I guess...
Any ideas on a solution would be appreciated.
Thanks & Regards
Indrajit
Downloaded & Installed a custom ROM zip, it worked. How can I make mine into a zip?
Most of the custom ROMs have a boot.img, system folder, data folder and meta-inf.
What is Meta-Inf?
Also If I zip my ROM (created as mentioned above) and try installing it doesnt since I dont have a Meta-Inf & I cant use the other meta-inf.
This is the ROM I installed: Worked fine except USB-PC connection didnt:
http://forum.xda-developers.com/showthread.php?t=1643736
Any ideas / suggestions would be highly useful & appreciated.
Thanks in advance.

[Q] How to make a rom from kernel.tar.gz file

Man I was trying to make a rom from source and I came across my kernel.tar.gz and ics.tar.gz file for my tc 88xx cpu
so how can I use those files to make a rom
Please help me man thanks in advance
karan1038 said:
Man I was trying to make a rom from source and I came across my kernel.tar.gz and ics.tar.gz file for my tc 88xx cpu
so how can I use those files to make a rom
Please help me man thanks in advance
Click to expand...
Click to collapse
To build a custom ROM extract the source code from the ics.tar.gz file (I would recommend using a program like 7-Zip). Once you have done that take the System folder that should be in the source code you extracted, create a new folder called MyROM, and put the source code for the System folder in the MyROM folder. Next extract the boot.img file for your ROM by extracting the boot partition of your stock ROM, and place it in the MyROM folder. Third, take a working META-INF folder that contains the standard Android update-binary, and a working updater script for your device, and place the META-INF folder in the MyROM folder. Once you have the System folder, Boot.img file, and META-INF folder in the MyROM folder, use 7-Zip to create a zip file containing the MyROM folder. After this flash the .zip file you created in recovery and you should have a custom. First off, for building a custom kernel if you extract the kernel source from the kernel.tar.gz file using 7-Zip, there should be a read-me or other type of documentation describing how to compile the kernel source code you downloaded. If there isn't any documentation I recommend taking a look at this guide on building your first kernel. While these are just a general outline of what you have to do, if you have any questions feel free to ask .
Re: [SOLVED] How to make a rom from kernel.tar.gz file
Shimp208
Man i can upload ics.tar.gz and kernel.tar.gz can you please help me to make an android rom
karan1038 said:
Shimp208
Man i can upload ics.tar.gz and kernel.tar.gz can you please help me to make an android rom
Click to expand...
Click to collapse
If you send me the links I will be happy to help you out and I'll try my best to assist you as best I can.
shimp208 said:
To build a custom ROM extract the source code from the ics.tar.gz file (I would recommend using a program like 7-Zip). Once you have done that take the System folder that should be in the source code you extracted, create a new folder called MyROM, and put the source code for the System folder in the MyROM folder. Next extract the boot.img file for your ROM by extracting the boot partition of your stock ROM, and place it in the MyROM folder. Third, take a working META-INF folder that contains the standard Android update-binary, and a working updater script for your device, and place the META-INF folder in the MyROM folder. Once you have the System folder, Boot.img file, and META-INF folder in the MyROM folder, use 7-Zip to create a zip file containing the MyROM folder. After this flash the .zip file you created in recovery and you should have a custom. First off, for building a custom kernel if you extract the kernel source from the kernel.tar.gz file using 7-Zip, there should be a read-me or other type of documentation describing how to compile the kernel source code you downloaded. If there isn't any documentation I recommend taking a look at this guide on building your first kernel. While these are just a general outline of what you have to do, if you have any questions feel free to ask .
Click to expand...
Click to collapse
Amazing!!!!
camy rock said:
Amazing!!!!
Click to expand...
Click to collapse
I should clarify that the source does not always include the /system folder sometimes companies will provide this and other times they won't. The other way to get the /system folder is to use adb and pull the system folder with a command similar to:
Code:
adb pull /system
Also this is just one example of a procedure that could be used to build a custom ROM from the stock ROM that originally ships with the phone. The procedure for building Cyanogenmod for example or another AOSP based ROM would be very different.
shimp208 said:
To build a custom ROM extract the source code from the ics.tar.gz file (I would recommend using a program like 7-Zip). Once you have done that take the System folder that should be in the source code you extracted, create a new folder called MyROM, and put the source code for the System folder in the MyROM folder. Next extract the boot.img file for your ROM by extracting the boot partition of your stock ROM, and place it in the MyROM folder. Third, take a working META-INF folder that contains the standard Android update-binary, and a working updater script for your device, and place the META-INF folder in the MyROM folder. Once you have the System folder, Boot.img file, and META-INF folder in the MyROM folder, use 7-Zip to create a zip file containing the MyROM folder. After this flash the .zip file you created in recovery and you should have a custom. First off, for building a custom kernel if you extract the kernel source from the kernel.tar.gz file using 7-Zip, there should be a read-me or other type of documentation describing how to compile the kernel source code you downloaded. If there isn't any documentation I recommend taking a look at this guide on building your first kernel. While these are just a general outline of what you have to do, if you have any questions feel free to ask .
Click to expand...
Click to collapse
what if the kernel source code doesnt have a system folder?
Got the same issue with alcatel pop 4 5051d
shimp208 said:
To build a custom ROM extract the source code from the ics.tar.gz file (I would recommend using a program like 7-Zip). Once you have done that take the System folder that should be in the source code you extracted, create a new folder called MyROM, and put the source code for the System folder in the MyROM folder. Next extract the boot.img file for your ROM by extracting the boot partition of your stock ROM, and place it in the MyROM folder. Third, take a working META-INF folder that contains the standard Android update-binary, and a working updater script for your device, and place the META-INF folder in the MyROM folder. Once you have the System folder, Boot.img file, and META-INF folder in the MyROM folder, use 7-Zip to create a zip file containing the MyROM folder. After this flash the .zip file you created in recovery and you should have a custom. First off, for building a custom kernel if you extract the kernel source from the kernel.tar.gz file using 7-Zip, there should be a read-me or other type of documentation describing how to compile the kernel source code you downloaded. If there isn't any documentation I recommend taking a look at this guide on building your first kernel. While these are just a general outline of what you have to do, if you have any questions feel free to ask .
Click to expand...
Click to collapse
So glad to see this thread. Mine is an alcatel pop 4 5051d. After extracting, i saw a .com file of about 650mb in size. Please, what do i do from here? d file: https://drive.google.com/uc?export=download&confirm=zM0d&id=0Byi69Jpw2ZDtcTFBX0FzMXBkajg

[Q] Compiling kernel from source and using zImage

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?

How create a new kernel

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?

Install kernel on galaxy ace 2?

Hi, I'm not sure if I have to flash the kernel partition with the kernel zImage or install the kernel in order to apply it? I am going to recompile the kernel with the swap option enabled, so it's basically a small change. Is there anything that I should know before I do this? How do I flash this? Is odin allright? BTW I have seen that the A2N kernel has a zip rom which is being installed from the cwm recovery. It has the kernel zImage placed as boot.img, in the root of the zip. It's strage to me, because I don't have boot.img in the partition mounted on / on the stock kernel, so where does it go? Or is the modified kernel being swapped with the stock one during boot-time?
zielonykid1234 said:
Hi, I'm not sure if I have to flash the kernel partition with the kernel zImage or install the kernel in order to apply it? I am going to recompile the kernel with the swap option enabled, so it's basically a small change. Is there anything that I should know before I do this? How do I flash this? Is odin allright? BTW I have seen that the A2N kernel has a zip rom which is being installed from the cwm recovery. It has the kernel zImage placed as boot.img, in the root of the zip. It's strage to me, because I don't have boot.img in the partition mounted on / on the stock kernel, so where does it go? Or is the modified kernel being swapped with the stock one during boot-time?
Click to expand...
Click to collapse
Convert your kernel into an Odin flashable zip using 7zip with its highest level of compression in tar format, make sure the file is converted into a .tar file or a .tar.md5 then flash that file via Odin in the AP or PDA slot. You might need to use a modified version of Odin.

Categories

Resources