Once you have those in the original folder just simply run the worker.txt file from the terminal, making sure you are in the worker folder directory.
#Extract .img file zip#
zip ROM file, and place them in the original folder. I have only been able to test with my S3 Mini, but should work with any ROM that has boot.img and system.img But it makes things a lot quicker and easier. I've named it worker as it does all the work for you, and it is just simply a bash script. To make things simpler I've created a script that automates almost the whole process. I've been playing around with adding root to my stock ROM these past few days, and have found it very slow and tedious trying to remember all the commands to unpack and repack the images. I just hex grepped it for a gzip signature indicating the start of the gzipped cpio ramdisk portion.Īutomated system/boot.img unpack/repack script Hello everyone, I normally use the tools found in this thread:īut like I said, your image was corrupt or something.
Do you want me to attach it for you? I assume you extracted the kernel OK (it worked for me).Ĭan you tell me, with which tools you managed to extract the kernel ?
#Extract .img file archive#
The boot.img doesn't use yaffs2, it is a raw kernel image combined with a cpio archive of the ramdisk image (and a short header to tell where the files are delimited). I used the script split_, split_ and unyaffs.exe What is it from and how did you extract it?įirmware: V845 V100R001MYSC02B 236(Malaysia) Or it is using some non-standard means to store the ramdisk. That img file is corrupt, or does not have a ramdisk image within it (only a kernel). I have tried it under windows and ubuntu, but still the same :( but when i want to extract the boot.img, then i have many errors and the. I have extracted with perl script the boot.img from updata.app Can somebody extract this boot.img please hi,