Posted by leszczu8023 on 02:09 android kitchen , boot image , boot.img , mediatek , mtk , nexus , recovery.img , zimage 3 comments if you must edit ramdisk or replace zimage in you boot image you don't need to reboot into linux or install cygwin environment!. Morpheus@zephyr (~)$ imgtool usage: imgtool _img_name_ [extract] where: _img_name_ is the name of an android boot or bootloader image (or boot partition) [extract] is an optional parameter to extract the image components. Opensuse: sudo zypper install android-tools; fetch the boot.img file. extract the boot.img either from rom .zip file or directly from the device: from the stock rom .zip file: some applications like supersu may modify the boot.img directly on the device, replacing it with the stock one would break such applications..
It's called bootimg.exe and was created by cofface,thanks.it's used to extract boot.img kernel/ramdisk for porting roms. it can run on windows. usually you extract stock boot.img and put the ^kernel^ into porting boot.img , and then repack!. The modified system images can easily be distributed as mtk extractor allows you to repack the firmware back to its original state. mtk extractor also allows you to unpack boot img files. for compatile devices, you can unpack the boot file of the firmware. download bluestacks 4 for windows – run android.... Unpack and repack the android boot & recovery images this is a tool i made for unpacking, repacking, and loki patching the android boot and recovery images. perfect for making a kernel developer's life a little easier or the beginner that just wants to unsecure their own boot image and/or add init.d support..
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.