• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

[TOOL][LINUX] boot.img kitchen

9 posts in this topic

Posted · Report post

Thought I'd share a simple kitchen for unpacking/packing boot.img that I've been using for ages. It might be helpful for some people. This is based on TigTex's ZTE Racer boot kitchen, which I've modified to suit my needs.

You need to have few basic packages installed in your system (perl, cpio, gzip and zip), which most already do. I've added an adb push boot.img to phone function which is experimental but working (you need to have adb shell root access and your sdcard needs to be mounted).

Place the boot.img you want to edit inside the bootkitchen folder. Run the script with:


./start.sh
[/code]

Select 1 to decompress the ramdisk and kernel from the boot.img

Select 2 to create a new boot.img from kernel and ramdisk

Select 3 to create a update.zip to flash with ClockWorkMod

Select 4 to adb push boot.img to phone (experimental)

Replace the zImage or modify the ramdisk. All made easy.

Useful information on splitting boot.img for those who are more interested.

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images

bootkitchen.zip

3

Share this post


Link to post
Share on other sites

Posted · Report post

Thanks!Something very helpful to make compiling a kernel very easy for many people! :D

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Thank you! I have little doubt, then Option 1. To use this option have to have the boot.img file in the folder bootkitchen? I need some more file there? Sorry the basic questions, I'm at the beginning :)

Edit: I've seen in the post TigTex

"How to use:

* Place your boot.img in the same folder as you extracted the kitchen (windows or linux folder)"

Edited by asm19
0

Share this post


Link to post
Share on other sites

Posted · Report post

I don't dig those kind of scripting tools as you would be missing out the real going on's underneath the bonnet so to speak. Not intending to start flamewars or anything like it, Sure it saves keystrokes but ...

  1. split_bootimg.pl # Perl script to extract the kernel and ramdisk
  2. gzip -dc boot.img-ramdisk.gz | cpio -i # to decompress the ramdisk
  3. mkbootfs TEMP_RAMDISK | gzip > modified_ramdisk.gz # to recreate the ramdisk
  4. mkbootimg --kernel ... --ramdisk ... --base 0x2600000 --cmdline '...' --o modifiedboot.img

This re-inforces and drills into your mindset on what is it doing and more importantly - understanding what is going on. Once its assimilated - you will never forget it! Those wrapper tools, reminds me of the days of old DOS, using Norton's BE command to soup up batch files, pass it through BAT2EXE to make it executable (If you're old enough to remember :P)

What am really saying those so-called wrappers around it are really convoluted and impose restrictions - what if you want to change the name of the directory for the extracted ramdisk, or even tweak the updater script...

0

Share this post


Link to post
Share on other sites

Posted · Report post

Thank you! I have little doubt, then Option 1. To use this option have to have the boot.img file in the folder bootkitchen? I need some more file there? Sorry the basic questions, I'm at the beginning :)

Same folder where the start.sh is.

0

Share this post


Link to post
Share on other sites

Posted · Report post

I'm using dsixda's kitchen, it has also got boot.img tools. ;)

But that's awesome too!

0

Share this post


Link to post
Share on other sites

Posted · Report post

I don't dig those kind of scripting tools as you would be missing out the real going on's underneath the bonnet so to speak. Not intending to start flamewars or anything like it, Sure it saves keystrokes but ...

  1. split_bootimg.pl # Perl script to extract the kernel and ramdisk
  2. gzip -dc boot.img-ramdisk.gz | cpio -i # to decompress the ramdisk
  3. mkbootfs TEMP_RAMDISK | gzip > modified_ramdisk.gz # to recreate the ramdisk
  4. mkbootimg --kernel ... --ramdisk ... --base 0x2600000 --cmdline '...' --o modifiedboot.img

This re-inforces and drills into your mindset on what is it doing and more importantly - understanding what is going on. Once its assimilated - you will never forget it! Those wrapper tools, reminds me of the days of old DOS, using Norton's BE command to soup up batch files, pass it through BAT2EXE to make it executable (If you're old enough to remember :P)

What am really saying those so-called wrappers around it are really convoluted and impose restrictions - what if you want to change the name of the directory for the extracted ramdisk, or even tweak the updater script...

I totally understand your point. Like I said, some people might find this useful. There plenty of people who don't have to get into a mindset of remembering these commands for the rest of their lives. They just need something simple to do get the job done. Of course things like these have certain limitations and people who are interested in what's going on underneath the bonnet can dig into the kitchen script itself.

I remember how difficult it was even to find the needed tools (split_bootimg.pl, mkbootfs and mkbootimg) when I wanted do this for the first time. Now they are all nicely bundled in the bin directory.

Here is also good information on splitting boot.img, which I've already linked several times on questions about this matter. This thread will probably save me some time in the future. ;)

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images

0

Share this post


Link to post
Share on other sites

Posted · Report post

I don't dig those kind of scripting tools as you would be missing out the real going on's underneath the bonnet so to speak. Not intending to start flamewars or anything like it, Sure it saves keystrokes but ...

  1. split_bootimg.pl # Perl script to extract the kernel and ramdisk
  2. gzip -dc boot.img-ramdisk.gz | cpio -i # to decompress the ramdisk
  3. mkbootfs TEMP_RAMDISK | gzip > modified_ramdisk.gz # to recreate the ramdisk
  4. mkbootimg --kernel ... --ramdisk ... --base 0x2600000 --cmdline '...' --o modifiedboot.img

This re-inforces and drills into your mindset on what is it doing and more importantly - understanding what is going on. Once its assimilated - you will never forget it! Those wrapper tools, reminds me of the days of old DOS, using Norton's BE command to soup up batch files, pass it through BAT2EXE to make it executable (If you're old enough to remember :P)

What am really saying those so-called wrappers around it are really convoluted and impose restrictions - what if you want to change the name of the directory for the extracted ramdisk, or even tweak the updater script...

And how many of the readers would just copypaste that :D But to have one of these scripts around won't hurt and I've actually learned quite a bit reading through stuff like these. However, I do understand and agree with the point you make :)

0

Share this post


Link to post
Share on other sites

Posted · Report post

I only made this tool because I was compiling a 2.6.35 kernel version to zte racer and it would require to do a lot of boot.img files for testing. Pressing 1 2 3 is easier than writing the same scripts or searching for them on the history. Nice to see that someone finds a use for this :P

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.