• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

How to repack with mkbootimg for windows

aio developers

aio developers

Android Enthusiast
pls how can i repack with mkbootimg.exe for windows:(.
i can unpack with unpackbootimg.exe but cant repack for windows
 
SPEEDEVS said:
pls how can i repack with mkbootimg.exe for windows:(.
i can unpack with unpackbootimg.exe but cant repack for windows
Click to expand...

mkbootimg is a linux command line tool for developers. You need knowledge of the command line and also the structure of a boot.img.

mkbootimg is used in conjunction with mkbootfs and unpackbootimg.

1. mkbootfs repacks the ramdisk.
2. mkbootimg repacks the kernel with the ramdisk which is how you get the boot.img.
3. unpackbootimg unpacks the kernel from the ramdisk.
4. gunzip(linux utility) unpacks the ramdisk.

To repack the boot.img you have to know all the parameters available to that kernel which you get during the unpack. You then use those parameters to repack the boot.img.

I will not be writing a tutorial for this as it would be too long. This is why I wrote a linux tool for developers to make this process simple.

To get all the parameters available in the version of mkbootimg you are using you simply run the following command...

Bash: 
./mkbootimg --help

I have compiled the latest versions of these utilities with android 9 pie support. You can get them from my repo here...
https://github.com/GameTheory-/mktool/tree/master/tools

My recommendation is to switch to or dual boot linux and learn to use it as it is the best platform for an all around android developer.
 
GameTheory said:
mkbootimg is a linux command line tool for developers. You need knowledge of the command line and also the structure of a boot.img.

mkbootimg is used in conjunction with mkbootfs and unpackbootimg.

1. mkbootfs repacks the ramdisk.
2. mkbootimg repacks the kernel with the ramdisk which is how you get the boot.img.
3. unpackbootimg unpacks the kernel from the ramdisk.
4. gunzip(linux utility) unpacks the ramdisk.

To repack the boot.img you have to know all the parameters available to that kernel which you get during the unpack. You then use those parameters to repack the boot.img.

I will not be writing a tutorial for this as it would be too long. This is why I wrote a linux tool for developers to make this process simple.

To get all the parameters available in the version of mkbootimg you are using you simply run the following command...

Bash: 
./mkbootimg --help

I have compiled the latest versions of these utilities with android 9 pie support. You can get them from my repo here...
https://github.com/GameTheory-/mktool/tree/master/tools

My recommendation is to switch to or dual boot linux and learn to use it as it is the best platform for an all around android developer.
Click to expand...
i know this but in carliv image kitchen for winsdows in the Bin folder there is a file called Mkbootimg.exe that can be run with command line and also unmkbooting too that i use i was able to use unpack or unmkbootimg but not able to use mkbootimg.exe in windows ,Thanks for the Support:)
 
You're not understanding. Mkbootimg.exe is most likely the linux version that was converted to windows format.

As such you still need to know how to repack the ramdisk first so that you can then use Mkbootimg.exe to repack the ramdisk and kernel into a boot.img.

The repack command can be long. Here's a short sample of the command with just 3 parameters...

Bash: 
./mkbootimg --kernel zImage --ramdisk ramdisk.gz -o boot.img

You would have to convert the above command for windows.

Here are all the parameters you can use with the above command depending on the kernel...

Code: 
usage: mkbootimg
       --kernel <filename>
       [ --ramdisk <filename> ]
       [ --second <2ndbootloader-filename> ]
       [ --recovery_dtbo <recoverydtbo-filename> ]
       [ --cmdline <kernel-commandline> ]
       [ --board <boardname> ]
       [ --base <address> ]
       [ --pagesize <pagesize> ]
       [ --dt <dtb-filename> ]
       [ --kernel_offset <base offset> ]
       [ --ramdisk_offset <base offset> ]
       [ --second_offset <base offset> ]
       [ --tags_offset <base offset> ]
       [ --os_version <A.B.C version> ]
       [ --os_patch_level <YYYY-MM-DD date> ]
       [ --header_version <version number> ]
       [ --hash <sha1(default)|sha256> ]
       [ --id ]
       -o|--output <filename>
 
GameTheory said:
You're not understanding. Mkbootimg.exe is most likely the linux version that was converted to windows format.

As such you still need to know how to repack the ramdisk first so that you can then use Mkbootimg.exe to repack the ramdisk and kernel into a boot.img.

The repack command can be long. Here's a short sample of the command with just 3 parameters...

Bash: 
./mkbootimg --kernel zImage --ramdisk ramdisk.gz -o boot.img

You would have to convert the above command for windows.

Here are all the parameters you can use with the above command depending on the kernel...

Code: 
usage: mkbootimg
       --kernel <filename>
       [ --ramdisk <filename> ]
       [ --second <2ndbootloader-filename> ]
       [ --recovery_dtbo <recoverydtbo-filename> ]
       [ --cmdline <kernel-commandline> ]
       [ --board <boardname> ]
       [ --base <address> ]
       [ --pagesize <pagesize> ]
       [ --dt <dtb-filename> ]
       [ --kernel_offset <base offset> ]
       [ --ramdisk_offset <base offset> ]
       [ --second_offset <base offset> ]
       [ --tags_offset <base offset> ]
       [ --os_version <A.B.C version> ]
       [ --os_patch_level <YYYY-MM-DD date> ]
       [ --header_version <version number> ]
       [ --hash <sha1(default)|sha256> ]
       [ --id ]
       -o|--output <filename>
Click to expand...
Thanks ,but hash hard to know since it doesnt come with the unmkbootimg.... i will use this to unpack then Maybe kernel Modifying or soo....easily Thanks
 
You must log in or register to reply here.
Back
Top Bottom