Hello,
I used RKdump_106 to extract/dump the firmware from my RK3328 TV box, so I have several *.IMG files.
I modified the bootanimation.zip in the system.img file. Now I do not know how to repack system.img and recreate a firmware.img that integrates all IMG files (boot, kernel, oem, recovery, resource, security, system, uboot, vendor, etc ...) in order to flash changes on the box.
Thanks for your help :fingers-crossed:
hi,
how did you Extract/Repack the system.img?
I have tested several tools and generally have a corrupt file type error message.
Even if the extraction seems to be done correctly.
Thank you.
Related
hi,
i have a big problem.
i have extracted with perl script the boot.img from updata.app
this works fine... but when i want to extract the boot.img, then i have many errors and the .gz files are not readable.
i have tried it under windows and ubuntu, but still the same :-(
can somebody extract the file ?
here is the .img file
http://www.megaupload.com/?d=XX69Z7BM
many thanks
That img file is corrupt, or does not have a ramdisk image within it (only a kernel). Or it is using some non-standard means to store the ramdisk.
What is it from and how did you extract it?
thanks for your replay
the file is from a v845 (huawei 8120).
Firmware: V845 V100R001MYSC02B 236(Malaysia)
from here: huawei
i used the script split_updata.pl, split_bootimg.pl and unyaffs.exe
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). Your file has a corrupt header. I was able to extract it for you. Do you want me to attach it for you? I assume you extracted the kernel OK (it worked for me).
Gene Poole said:
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). Your file has a corrupt header. I was able to extract it for you. Do you want me to attach it for you? I assume you extracted the kernel OK (it worked for me).
Click to expand...
Click to collapse
yes, please attach it
can you tell me, with which tools you managed to extract the kernel ?
thanks
wildgunman said:
yes, please attach it
can you tell me, with which tools you managed to extract the kernel ?
thanks
Click to expand...
Click to collapse
I normally use the tools found in this thread:
http://forum.xda-developers.com/showthread.php?t=551711
but like I said, your image was corrupt or something. I just hex grepped it for a gzip signature indicating the start of the gzipped cpio ramdisk portion.
I am a beginner, and I have compiled a game built with C. The instructions I have say that I have to flash the final .img file to a separate partition on my SM-N900P. Now I have successfully downloaded the stockfirmware, unpacked it with mkbootimg, built my own dtb.img and flashed the phone. (Side note: I got an error about Samsung Keyboard, which if you know how I can address I would be grateful). I do not know how / where to put the .img file I compiled though. Do I pack it when I tar my files?
I managed to dd the recovery image from partition.
I tried use lot of tools from web mkbootimg, extractor, unpack and etc.
But none of it able to extract it contents. Dont know WTF how it build.
I only managed to use binwalk to extract the ramdisk folder but no kernel file,
so without kernel file I'm no able to pack it back.
recovery.img attached below,
Please help, XDA expert around the world. Thanks
https://drive.google.com/open?id=0B9J7sutBoCFlcHRVWUpCUEFZWm8
It's a .img, use 7zip.
Or just mount it to a virtual disk drive.
can you write in system of sharp 404sh?
Please guide for me...
thankyou very much....
[email protected]
me too
Hey all, I've looked all over an can't find the answer to this... I have a NAND backup I made using TWRP, however, I had the problem many have had with getting errors when trying to restore it. So I thought I'd try a different way by creating a TWRP flashable file from the NAND files. I have taken the files from the backup and extracted them using CYGWIN. I read a thread here:
https://forum.xda-developers.com/showthread.php?t=2746044
But I'm stuck on a couple of things... First, the part about using the META-INF folder from another ROM... I've checked the files in in the META-INF folder and notice that the updater-script is what loads the files and directories. But none of the META-INF files I have found matches my backup files.
The files I want to flash are the complete system folder, complete data folder and the boot.img file. Is it possibly to flash these with TWRP without the META-INF folder/files? If I have to use the META-INF how do I make sure all the files and folders are flashed?
Would it be better to create an ODIN flashable file and just use Odin to do the flash? If so should I put the system and data folders into one file and then use the boot.img (or would I put the boot.img finle into a tar) in the Bootloader spot in Odin?
Thanks in advance.
I have used LGUP and selected all partitions from DUMP. Is it enough if something goes wrong, do I have everything I need? It must have specific extension?
Yes you have everything you need. Partitions dont need a file extension you can add .img to the file names if you want, which will make them image files. They can all be flashed via fastboot or twrp using console commands just the way they are.