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.
Related
I wanted to add some extra steps to my init.rc file but was unsuccessful. I was hoping someone could explain what I'm doing wrong or advise if there is a better way to do this.
I started by creating a new backup image using clockworkmod and then copied the boot.img file over to my host. I then used the steps as described in the thread "HOWTO: Unpack, Edit, and Re-Pack Boot Images" to unpack the contents and get the init.rc file. After adding the additional steps at the end, I packaged the boot.img file back up using mkbootfs and mkbootimg and then pushed the file to my sdcard. However, when I try to use "flash_image" to flash the new boot.img, I always get the error "error scanning partition". I don't think the problem is with the new boot.img file because I get the same error if I try to flash the original boot.img or even some non-existing file.
I also tried to simply replace the original boot.img file in my clockworkmod back up directory and do a standard restore, but that doesn't get past the "Viewsonic" logo screen. I assume that is because of some checksum issue.
Can anyone see my error or suggest and alternate method?
Thanks in advance
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
After unpacking boot.img using cygwin and kitchen. I didint get ramdisk folder. How can I fix this?
Need some help. I'm trying to do this thing. Repack boot.img (unpack image, unpack ram archive, modify it, add my files to image, pack ram, pack boot.img). Flash my own repacked boot.img with heimdall to device, everything was okay, i can see files on my device after reboot. But when I try to start my file /my_bin it write 'Permission denied', same thing when I try to read it with cat (for example, cat /my_bin). Rights for file are 755 (rwxr-xr-x), everybody can run it. If i understand correctly SELinux configuration restrict my access to this files. I'm trying to copy /my_bin file in init.rc to different folder, but this doesn't help. Can i modify SELinux context from init.rc or modify it when repacking boot.img (i'm think contexts are in file_contexts.bin, but i don't know yet how to modify this binary file). Or something else?
Nobody?
Hello,
I've followed this tutorial (https://forum.xda-developers.com/t/...r-img-and-flashing-our-modifications.4196625/) to extract system.img from super.img and edit it. So far, I was able to extract system.img from super.img and mount it to a folder in fedora. The problem is I cannot modify the files, I tried all ways I could think about but had no luck as the source is write-protected, so it only mounted it as read-only. I tried to copy all the files to different folder using rsync, but the system.img file is getting bigger than original and when I make it to super.img with lpmake, the phone doesn't work and stuck in bootloop. Does anyone has any idea about this?
Thank you