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.
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!
Can anyone link me to a guide or explain here how to convert an ASUS Stock .zip ROM to a Flashable zip that can be flashed in recovery ?
I managed to get my hands on the final Stock Honeycomb 8.6.5.21 ROM ASUS released before moving over to ICS and want to create a flashable .zip so I can flash it in recovery like any other custom ROM
Thanks
*Detection* said:
Can anyone link me to a guide or explain here how to convert an ASUS Stock .zip ROM to a Flashable zip that can be flashed in recovery ?
I managed to get my hands on the final Stock Honeycomb 8.6.5.21 ROM ASUS released before moving over to ICS and want to create a flashable .zip so I can flash it in recovery like any other custom ROM
Thanks
Click to expand...
Click to collapse
No, you cant. But you can take your /system (ROM) files and compress it as .tar file from the Terminal Emulator. You need know how to make an updater-script to make the zip file flashable from custom recovery. Try to use the Android Kitchen
TheMrcool212 said:
No, you cant. But you can take your /system (ROM) files and compress it as .tar file from the Terminal Emulator. You need know how to make an updater-script to make the zip file flashable from custom recovery. Try to use the Android Kitchen
Click to expand...
Click to collapse
It's packed as a blob so not as easy as extracting it I suppose, I've read a little about extracting blob files but never tried it
Thanks for the info, I`ll leave the link to it here if anyone fancies giving it a shot
http://www.portableandroid.co.uk/androidDL/WW_epad-user-8.6.5.21.zip
One way is to extract the blob from the zip ( which is actually a zip within a zip ) and write it to disk from a terminal I'm assuming you are rooted as you mention having CWM . The command off the top of my head is: dd if=/pathtoyourblobfile of=/dev/block/mmcblk0p4. It will take a few minutes to complete, bear in mind you will be back to stock, I.e. no CWM and you will lose root. HTH.
pkfox said:
One way is to extract the blob from the zip ( which is actually a zip within a zip ) and write it to disk from a terminal I'm assuming you are rooted as you mention having CWM . The command off the top of my head is: dd if=/pathtoyourblobfile of=/dev/block/mmcblk0p4. It will take a few minutes to complete, bear in mind you will be back to stock, I.e. no CWM and you will lose root. HTH.
Click to expand...
Click to collapse
That's why I wanted a flashble zip, so I don't return to stock and can easily flash back to 4.2.2 when I'm done playing
Cheers though
What I did was backup 4.2.2, then flash stock (recovery and ROM).
Then I rooted and installed TWRP using Wolf's method 3.
Made a stock backup in TWRP.
Then I can restore to stock, and when I'm done I can restore back to 4.2.2
You can take your ROM files by doing these commands in the Terminal Emulator.
Code:
su
tar -c system/* >> sdcard/system.tar
And wait for few minutes and a file named system.tar will appear in /sdcard. You can take the file from your computer and use the android kitchen to make the /system file flashable in custom recovery. You can find the tutorial (Here)
frederuco said:
What I did was backup 4.2.2, then flash stock (recovery and ROM).
Then I rooted and installed TWRP using Wolf's method 3.
Made a stock backup in TWRP.
Then I can restore to stock, and when I'm done I can restore back to 4.2.2
Click to expand...
Click to collapse
Good idea, so does the TF see the HC update zip and just allow you to flash as if it was an OTA, even from JB or did you need to flash it a different way ?
TheMrcool212 said:
You can take your ROM files by doing these commands in the Terminal Emulator.
Code:
su
tar -c system/* >> sdcard/system.tar
And wait for few minutes and a file named system.tar will appear in /sdcard. You can take the file from your computer and use the android kitchen to make the /system file flashable in custom recovery. You can find the tutorial (Here)
Click to expand...
Click to collapse
Great thanks, I`ll take a look at that method too cheers
*Detection* said:
Good idea, so does the TF see the HC update zip and just allow you to flash as if it was an OTA, even from JB or did you need to flash it a different way ?
Click to expand...
Click to collapse
I flashed the last ICS firmware (unzip once) from TWRP. Should work the same from HC.
Then install TWRP using ADB or APX. Root if you want (flash SuperUser.zip) and make a nandroid.
frederuco said:
I flashed the last ICS firmware (unzip once) from TWRP. Should work the same from HC.
Then install TWRP using ADB or APX. Root if you want (flash SuperUser.zip) and make a nandroid.
Click to expand...
Click to collapse
Ah so the stock zips are already flashable from TWRP, shame theres not a simple way to add TWRP to the stock zip
[Q] I am trying to do some kernel mods on my GSIII running 4.1.4. or later. I am used to using an older version of heimdall and an older version of Android, and simply flashing the zImage into the --kernel partition. I know the new version of heimdall uses the phones names for the partitions, and the partition has changed from KERNEL to something else, but I can't really figure out what.
The partitions I see are BOOTLOADER, TZSW, PIT, MD5HDR, BOTA0, BOTA1, EFS, PARAM, BOOT, RECOVERY, RADIO, CACHE, SYSTEM, HIDDEN, OTA, and USERDATA.
Should I flash the zImage to one of these partitions, or do I have to create a zip file with the zImage, modules, and other stuff to make an image loadable with a rom manager?
Anyone have vendor_boot, dtbo and boot.img from 11.2.9.9 le25aa ?. Install a custom kernel and I need to go back to stock
Just use oxygen updtaer to download full zip and do a local install. Flash magisk to alternate partition and reboot.
gorilla p said:
Just use oxygen updtaer to download full zip and do a local install. Flash magisk to alternate partition and reboot.
Click to expand...
Click to collapse
Install the Arter kernel. And now I get an error when I want to update that way. So I need to go back to stock rom.
Do you know any way to do that?
Partigiano0105 said:
Install the Arter kernel. And now I get an error when I want to update that way. So I need to go back to stock rom.
Do you know any way to do that?
Click to expand...
Click to collapse
Shouldn't be flashing a kernel without proper backups first. You need stock untouched boot.img and vendor_boot
mattie_49 said:
Shouldn't be flashing a kernel without proper backups first. You need stock untouched boot.img and vendor_boot
Click to expand...
Click to collapse
how can I do that?
You can download the zip file containing th full update of your version in a thread here, them using the payload dumper tool you extract all img files inside
I don't know how to edit so more details about this process:
1. Go to sticked thread Repo of oos builds
2. Download the zip file of the firmware you are using
3. Download the payload dumper here: https://androidfilehost.com/?fid=818070582850510260
4. Once extracted extract the payload.bin from firmware zip into payload_input directory
5. Launch payload_dumper.exe
6. Process take few minutes depending on your computer, result img files are stored in payload_output directory
7. Have fun with your img file
Hello,
I'm just getting into Android, and I've been messing around with boot.img with Magisk.
The boot.img that I'm specifically looking at is Pixel 6a.
I used `magiskboot unpack boot.img`, but I only got a kernel file.
Now, I'm wondering where the ramdisk.cpio. From what I read, ramdisk determines what to mount and whatnot.
Even without a ramdisk, I can fastboot flash boot boot.img it to my device and it will still work.
If there is no ramdisk in boot.img, then how does the device know what to mount or what the file hierarchy is when I flash it?
If the stock boot.img doesn't have a ramdisk, does not mean I have to generate my own?
Thanks!
init is on system, no ramdisk required.
https://source.android.com/docs/core/architecture/partitions/system-as-root#sar-partitioning
alecxs said:
init is on system, no ramdisk required.
https://source.android.com/docs/core/architecture/partitions/system-as-root#sar-partitioning
Click to expand...
Click to collapse
does that mean if I do include ramdisk.cpio, it overrides the one on system?
Yes, if you modify the kernel so ramdisk is extracted and processed (that's what Magisk does)
alecxs said:
Yes, if you modify the kernel so ramdisk is extracted and processed (that's what Magisk does)
Click to expand...
Click to collapse
Thank you so much for the link. I read up on it, and as you said, boot.img just carries a kernel file and ramdisk is in system.img.
It looks like you can also unpack, modify, and repack system.img and flash it onto pixel devices, so do you know why Magisk decided to create ramdisk.cpio and repack it into boot.img when it could have modified system.img? Is it because boot.img has a kernel file?
Thanks
Magisk also mods the DTB from "skip_initramfs" to "want_initramfs".
drunk_santa said:
It looks like you can also unpack, modify, and repack system.img and flash it onto pixel devices, so do you know why Magisk decided to create ramdisk.cpio and repack it into boot.img when it could have modified system.img?
Click to expand...
Click to collapse
Because Magisk is systemless-root method
https://topjohnwu.github.io/Magisk/boot.html