Does anyone know how to extract and repack system.img file that comes from factory image KTU84P?
I've been using windows 7, should i use ubuntu?
Related
First of all, what Im trying to do is to extract the .tar.md5 files that come with every ROM.
Every time I do that I get a message from 7-zip "There is no correct record at the end of the archive", however the files are extracted.
Below are the files inside the extracted folder:
boot.img
recovery.img
system.img
userdata.img
Then I try to open the system.img with unyaffs but I get some errors there too for example: STATUS_ACCESS_VIOLATION.
So my questions are:
1) How to correctly extract a .tar.md5 file?
2) How to open a yaffs2 .img file?
Thanks
try on RAR.
I tried with Rar, but still the same
Anyone know how to repack boot.img file using Kitchen? I open up menu of the kitchen, enter 0 for advance menu and enter 12 for boot.img tools. And i unpack it there and i edit the init.rc and now changed the working folder of unpacked image by "BOOT-EXTRACTED" and now i get an error of working folder not found. How can i do this? Thanks.
After unpacking boot.img using cygwin and kitchen. I didint get ramdisk folder. How can I fix this?
im trying to extract the contents of the tar file
i need the
boot.img
system.img
recovery.img
if some could please do that
it says corrupted file each time
robertisnoob said:
im trying to extract the contents of the tar file
i need the
boot.img
system.img
recovery.img
if some could please do that
it says corrupted file each time
Click to expand...
Click to collapse
What are you using to extract the files?
robertisnoob said:
im trying to extract the contents of the tar file
i need the
boot.img
system.img
recovery.img
if some could please do that
it says corrupted file each time
Click to expand...
Click to collapse
Using winrar / 7zip you can extract files.
I have converted sparsechunks to a single system.img. Then extracted that system.img and modified it. Now how to convert the folder to system.img again? I have tried mtk extractor which actually failed but didn't show any log.