simg2img

在 IBM Server 上：

[root@localhost cm-13-kiwi-4-honor5x]# which simg2img

/opt/android-x86/cm-13-kiwi-4-honor5x/out/host/linux-x86/bin/simg2img

[root@localhost cm-13-kiwi-4-honor5x]# which make_ext4fs

/opt/android-x86/cm-13-kiwi-4-honor5x/out/host/linux-x86/bin/make_ext4fs

[root@localhost cm-13-kiwi-4-honor5x]#

++++++++++++++++++++++++++++++++++++++++++++++++++++++++

http://stackoverflow.com/questions/8663891/how-to-mount-the-android-img-file-under-linux

This is for all who wants to unpack and modify the original system.img that you can flash using recovery.

system.img (what you get from the google factory images for example) represents a sparsed ext4 loop mounted file system.

It is mounted into /system of your device. Note that this tutorial is for ext4 file system, you may have system image which is yaffs2 for example.

the way it is mounted on Galaxy Nexus:

“/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0″ Prerequisites:

Linux box or virtual machine simg2img, make_ext4fs binaries which can be downloaded from herehttp://andwise.net/?attachment_id=406

Procedure:

place you system.img and the 2 binaries in one directory, and make sure the binaries have exec permission. Part 1 – mount the filesystem

mkdir sys
./simg2img system.img sys.raw
mount -t ext4 -o loop sys.raw sys/

Then you have all your system partition mouned in ‘sys’ and you can modify whatever you want in ‘sys’. For example de-odex apks and framework jars. Part 2 – create a new flashable system image.

./make_ext4fs -s -l 512M -a system new.img sys/

 umount sys

rm -fr sys

Now you can simply type:

fastboot flash system new.img

++++++++++++++++++++++++++++++++++++++++