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!
Defy officially doesn't have support for CWM Touch, who other devices have. However, there is a few devices with similar hardware with official support like Optimus Black.
Maybe with porting this, we can have a full compatibility with nandroids made by original CWM Recovery.
Right now, i have extracted ramdisk from CWM Touch Recovery, but really don't know which files a have to touch in order to port sucessfully to our Defy.
A little research about it, show me that i have to make changes in:
+ default.prop
+ init.rc
+ ueventd.goldfish.rc
+ ueventd.rc
+ /etc/recovery.fstab
* and, make a new uevent.moto.rc instead of ueventd.lge.rc
Someone wants to join on this project?
i'm attaching files from extracted ramdisk.
This might help aswell
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html?m=1
I will try and build one tomorrow with this guide since i already have the cm source
You can't compile Touch-CWM because source currently is not public.
But Koush made a Builder: http://builder.clockworkmod.com/
Ich made a CWM-Version for our defy with his builder and compiled it to an update-package for our lovely bootmenu
This replaces "Custom Recovery"... Have Fun!
m11kkaa said:
You can't compile Touch-CWM because source currently is not public.
But Koush made a Builder: http://builder.clockworkmod.com/
Ich made a CWM-Version for our defy with his builder and compiled it to an update-package for our lovely bootmenu
This replaces "Custom Recovery"... Have Fun!
Click to expand...
Click to collapse
But this will only work with ics??? The builder page said so...
Enviado desde mi MB526 usando Tapatalk 2
m11kkaa said:
You can't compile Touch-CWM because source currently is not public.
But Koush made a Builder: http://builder.clockworkmod.com/
Ich made a CWM-Version for our defy with his builder and compiled it to an update-package for our lovely bootmenu
This replaces "Custom Recovery"... Have Fun!
Click to expand...
Click to collapse
oops my bad just realised it just for porting CWM if your device is not already supported .... thanks for the link m11kkaa...
espaciosalter20 said:
But this will only work with ics??? The builder page said so...
Enviado desde mi MB526 usando Tapatalk 2
Click to expand...
Click to collapse
Just flashed it and it works fine! I'm using ics with froyo kernel. It will work with any Rom because we only have froyo and gingerbread kernels. The version of cwm was 5.8.4.3. Remember that to use custom recovery you must launch it from the bootmenu, the reboot to recovery from the power menu launches the stable recovery.
Sent from my MB525 using Tapatalk 2
kadopt said:
Just flashed it and it works fine! I'm using ics with froyo kernel. It will work with any Rom because we only have froyo and gingerbread kernels. The version of cwm was 5.8.4.3. Remember that to use custom recovery you must launch it from the bootmenu, the reboot to recovery from the power menu launches the stable recovery.
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
I also installed the touch CWM recovery, it looks gud but not better than TWRP.
I tried to restore a nandroid made by normal cwm recovery but it showed MD5 mismatch, I restored the same nandroid with the help of normal recovery. It seems that more work needs to be done but its surely a very gud step forward.
m11kkaa said:
You can't compile Touch-CWM because source currently is not public.
But Koush made a Builder: http://builder.clockworkmod.com/
Ich made a CWM-Version for our defy with his builder and compiled it to an update-package for our lovely bootmenu
This replaces "Custom Recovery"... Have Fun!
Click to expand...
Click to collapse
You're right... it can't compile from source, but there is a workaround: Extract defy kernel from recovery.img of defy and modify the ramdisk that i provide, re-pack it in recovery.img with kernel extracted from defy recovery.img... That's why i was trying to modify the CWM official from another device.
Step by step to do this:
1. Use Linux
2. Get mkbootfs & mkbootimg
3. Get split_boot.zip
4. Grab a boot.img or recovery.img
5. Split it with following code:
Code:
./split_bootimg.pl recovery.img
Click to expand...
Click to collapse
6. Examine
7. You will have two new files based on whatever file name you gave above
kernel will have "-kernel"
YES this is the kernel (compressed) for this .img
you have successfully extracted the kernel
you cannot edit these
you can mix and match
if I know the kernel from older boot works I can just use it with my newly edited ramdisk
ramdisk will have "-ramdisk.gz"
feel free to rename
8. Unpack Ramdisk
Code:
mkdir ramdisk_recovery
cd ramdisk_recovery
gzip -dc ../recovery.img-ramdisk.gz | cpio -i
Click to expand...
Click to collapse
9. Examine
In all ramdisk you will have a few folders and files:
data
dev
etc
proc
res
images for recovery go here
sbin
the actually recovery binary goes here
also adbd
sys
system
tmp
default.prop
init
init.goldfish.rc
init.rc
init.yuhua.rc
init.yuhua.sh
initlogo.rle
10. Pack-up Ramdisk
Code:
mkbootfs ./ramdisk_recovery | gzip > ramdisk_recovery-edited.gz
Click to expand...
Click to collapse
11. Back to IMG
Code:
mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel recovery.img-kernel --ramdisk ramdisk_recovery-edited.gz -o recovery-edited.img
Click to expand...
Click to collapse
use file good file names! Or you might end up with many test tries and cannot figure out what you did for each
Here you can mix and match kernels
12. Now Flash via recovery or something
All files are attached in zip.
espaciosalter20 said:
But this will only work with ics??? The builder page said so...
Enviado desde mi MB526 usando Tapatalk 2
Click to expand...
Click to collapse
its bootmenu recovery
will work on any system
Sent from my MB526 using xda premium
espaciosalter20 said:
You're right... it can't compile from source, but there is a workaround: Extract defy kernel from recovery.img of defy and modify the ramdisk that i provide, re-pack it in recovery.img with kernel extracted from defy recovery.img... That's why i was trying to modify the CWM official from another device.
Click to expand...
Click to collapse
You know that defy has locked bootloader and we can't boot modified boot/recovery-images?
m11kkaa said:
You know that defy has locked bootloader and we can't boot modified boot/recovery-images?
Click to expand...
Click to collapse
That's partially true. We can't boot modified boot img but it is possible with modified recovery img because we don't mess up with kernel or bootloader. Other Motorola locked devices gets cwm touch officially and even we can't have cwm if modified recovery img was not supported.
Enviado desde mi MB526 usando Tapatalk 2
1) I still don't understand what your "solution" has todo with the fact that the source of Touch-CWM is not public and we only have a web-based builder.
2) Currently we start CWM through bootmenu which works fine and I don't know why you want to modify the stock recovery-image.
However you can't modify the recovery-image in anyway because the complete image is signed, and not the kernel only
Just reporting .....works perfectly with multiboot....but still prefer twrp over this....!!!
Sent from my MB525 using XDA
m11kkaa said:
1) I still don't understand what your "solution" has todo with the fact that the source of Touch-CWM is not public and we only have a web-based builder.
2) Currently we start CWM through bootmenu which works fine and I don't know why you want to modify the stock recovery-image.
However you can't modify the recovery-image in anyway because the complete image is signed, and not the kernel only
Click to expand...
Click to collapse
Cwm touch is a custom recovery. So, I don't want to replace stock recovery. Only porting this custom recovery to our defy.
Enviado desde mi MB526 usando Tapatalk 2
@espaciosalter20 : can u please test the recovery posted by m11kkaa and test if you wanted to do the same?
brajesh.sharma87 said:
@espaciosalter20 : can u please test the recovery posted by m11kkaa and test if you wanted to do the same?
Click to expand...
Click to collapse
m11kkaa made that recovery using builder page of koushik (maker of cwm). I'm going to try it, maybe that "Touch Recovery will only work on ICS and later kernels." wich is stated in builder page, isn't accurate.
espaciosalter20 said:
m11kkaa made that recovery using builder page of koushik (maker of cwm). I'm going to try it, maybe that "Touch Recovery will only work on ICS and later kernels." wich is stated in builder page, isn't accurate.
Click to expand...
Click to collapse
well I checked it on multiboot and it worked with both cm7 and cm9.
however they might be some bug which is not confirmed at the moment.
Does clockworkmod touch have any extra features compared to original? (Apart from touch input ) I ask because I switched over to teamwin last week and love it! The compression option leaves so much more space on my sdcard after backups, also the zip queuing is great and wipes of any kind are faster. My only complaint is it flashes CM7 builds about half the speed clockworkmod does it, but still an awesome recovery, only other problem I guess is if I got a soft brick and had to flash sbf there's no way to install it which means I would have to flash it after flashing 2ndinit, which is one advantage of this if its ported properly as I could restore a backup faster when disaster strikes
Sent from the real world by hacking into the matrix
@non4 said:
Does clockworkmod touch have any extra features compared to original? (Apart from touch input ) I ask because I switched over to teamwin last week and love it! The compression option leaves so much more space on my sdcard after backups, also the zip queuing is great and wipes of any kind are faster. My only complaint is it flashes CM7 builds about half the speed clockworkmod does it, but still an awesome recovery, only other problem I guess is if I got a soft brick and had to flash sbf there's no way to install it which means I would have to flash it after flashing 2ndinit, which is one advantage of this if its ported properly as I could restore a backup faster when disaster strikes
Sent from the real world by hacking into the matrix
Click to expand...
Click to collapse
no extra feature, its all same only touch included.
and dont u have normal cwm recovery in stable recovery? AFAIK Twrp replaces the custom recovery only, isn't it true?
brajesh.sharma87 said:
no extra feature, its all same only touch included.
and dont u have normal cwm recovery in stable recovery? AFAIK Twrp replaces the custom recovery only, isn't it true?
Click to expand...
Click to collapse
Actually it's the custom recovery that stays as clockworkmod for me, I have the touch bootmenu. But I mean the kind of soft brick where only bootloader and stock recovery work, and I don't know any way to.install teamwin from stock froyo without having clockworkmod to flash it
Sent from the real world by hacking into the matrix
I would like to install CM7 alpha9 MTD from this thread http://forum.xda-developers.com/showthread.php?t=2309390
The process I imagine is as following:
- backup things (I'm not sure how exactly this part works, if you know how to backup application data please help)
- flash the https://cm7-i5800.googlecode.com/files/CM7_Kernel_MTD_OC1Ghz.tar kernel with ODIN without repartitioning (as PDA I'm guessing, unless there's an option for "kernel" in which case it's kernel, which one is it? )
- boot to recovery
- format /system, /data, /preload
- install the ZIP of the ROM: https://cm7-i5800.googlecode.com/files/CM7.2.0-GT-I5800_Alpha9_MTD_CWM.zip
- install the ZIP of the google apps for 2.3.7: http://www.devfiles.co/download/wBDwQIzb/gapps-gb-20110828-newtalk-signed.zip
- install SuperSU ? is this necessary with CM? Although I have doubts, as it was never mentioned unlike for Omni, so I guess not for this one
- reboot phone
- enjoy CM7
So basically I'm asking, am I missing out on anything basic but important that would result in bricking? And
- how to backup application data to be retrieved after flashing
- is the kernel a "PDA" or is there another thingy for it in Odin that needs be done?
- do you need to install any previous versions of CM7 for this MTD thing to work?
- does the kernel provide a recovery with which this ROM can be installed?
If you managed to get to the end, thank you - And thanks in advance for the help
Installing a rom
Zhuinden said:
I would like to install CM7 alpha9 MTD from this thread http://forum.xda-developers.com/showthread.php?t=2309390
The process I imagine is as following:
- backup things (I'm not sure how exactly this part works, if you know how to backup application data please help)
- flash the https://cm7-i5800.googlecode.com/files/CM7_Kernel_MTD_OC1Ghz.tar kernel with ODIN without repartitioning (as PDA I'm guessing, unless there's an option for "kernel" in which case it's kernel, which one is it? )
- boot to recovery
- format /system, /data, /preload
- install the ZIP of the ROM: https://cm7-i5800.googlecode.com/files/CM7.2.0-GT-I5800_Alpha9_MTD_CWM.zip
- install the ZIP of the google apps for 2.3.7: http://www.devfiles.co/download/wBDwQIzb/gapps-gb-20110828-newtalk-signed.zip
- install SuperSU ? is this necessary with CM? Although I have doubts, as it was never mentioned unlike for Omni, so I guess not for this one
- reboot phone
- enjoy CM7
So basically I'm asking, am I missing out on anything basic but important that would result in bricking? And
- how to backup application data to be retrieved after flashing
- is the kernel a "PDA" or is there another thingy for it in Odin that needs be done?
- do you need to install any previous versions of CM7 for this MTD thing to work?
- does the kernel provide a recovery with which this ROM can be installed?
If you managed to get to the end, thank you - And thanks in advance for the help
Click to expand...
Click to collapse
Reboot to recovery, make a backup (you'll find in the menu)
Make a full wipe(in recovery)
- install the ZIP of the ROM: https://cm7-i5800.googlecode.com/files/CM7.2.0-GT-I5800_Alpha9_MTD_CWM.zip
- install the ZIP of the google apps for 2.3.7: http://www.devfiles.co/download/wBDwQIzb/gapps-gb-20110828-newtalk-signed.zip
- flash the https://cm7-i5800.googlecode.com/files/CM7_Kernel_MTD_OC1Ghz.tar
Install all these 3 zip with One Package ticked
Reboot and enjoy
Good luck
to install CM7 alpha 9 MTD you first need to be running CM7 alpha 9, which you flash with ODIN http://forum.xda-developers.com/showpost.php?p=14240212&postcount=1
then follow the instructions in the previous reply from sakenas to update to CM7 alpha 9 MTD using clockwork mod recovery.
only flash the 1ghz kernel after you have updated to CM7 alpha9 MTD.
you flash the kernel with ODIN using the one package method, exactly the same way you will have flashed CM7 alpha 9.
After getting Resurrection Remix ROM (which comes with a kexec-hardboot patch kernel) I thought I'd try installing MultiROM. I got MultiROM manager from the Play Store and it detected fine that I had the kexec-hardboot patch kernel. I went ahead with the installation but in the terminal in the app it give me the message:
Code:
preparing downloads
Skipping already downloaded file TWRP_multirom-amami20150201-00.img
Skipping already downloaded file MultiROM-v30x-170115-unofficial-amami.zip
Installing file TWRP_multirom-amami20150201-00.img... SUCCESS
Installing file MultiROM-v30x-170115-unofficial-amami.zip... NEEDS RECOVERY
It then asks me to reboot but doing so does not install MultiROM. I first thought that this may be an issue with my ROM coming with the MultiROM modified TWRP but I have tried installing MultiROM and recovery separately and together multiple times to no avail.
any help would be greatly appreciated. Thanks in advance.
HI!
I pulled some files rom my Vivax tpc-101 3G to try porting a custom ROM. Since that didn't work out I wanted to post the files here for someone that might need a stock rom, kernel, recovery, twrp... or wanted to try porting a ROM.
Files included in this folder:
- stock kernel
- magisk kernel
- stock recovery
- twrp port from a porting tool
- TWRP backup of system
NOTES:
- Touch is not working correctly on TWRP (flipped and inverted touch)
- System backup is rooted with magisk and contains some build.prop tweaks. Changed boot animation.
DOWNLOAD:
- Drive Link
PS:
Could anyone make a flashable zip out of the twrp bakup? I tried but I don't know how to create the updater-script and there is no ROM for this tablet that I could use as a flashable zip base.