Hi, anyone knows how can i extract ramdisk img?
I tried with HuaweiUpdateExtractor but it don't showme that partition so i don't know what is wrong.
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 have a problem when make img file.
unyaffs img file create all folder and files from system.img. This stuff work without any issue.
Size of this folders and files is 317.4 MB.
When start to create new img file with mkfs.yaffs2, size of new img file is 2GB.
How to resolve this problem and create image file with properly filesize?
FileFixer said:
I have a problem when make img file.
unyaffs img file create all folder and files from system.img. This stuff work without any issue.
Size of this folders and files is 317.4 MB.
When start to create new img file with mkfs.yaffs2, size of new img file is 2GB.
How to resolve this problem and create image file with properly filesize?
Click to expand...
Click to collapse
You're doing something wrong. Make sure the image you are trying to unyaffs is in its own empty folder. After unyaffs remove the .img from that folder. Then create new image file by running the mkfs.yaffs2 as follows: mkfs.yaffs2 /home/killahurtz/Desktop/location of extracted system.img/ system.img
~/Desktop/newrom$ mkfs.yaffs2 /home/filefixer/Desktop/newrom/ system.img
mkfs.yaffs2: Android YAFFS2 Tool,Build by PowerGUI
at http://www.openhandsetalliance.org.cn
Building...
Build Ok.
Into newrom folder no system.img file when go to create image. Just unpacked files and folders without system.img.
After that, system.img is corectly created but have 2GB.
FileFixer said:
~/Desktop/newrom$ mkfs.yaffs2 /home/filefixer/Desktop/newrom/ system.img
mkfs.yaffs2: Android YAFFS2 Tool,Build by PowerGUI
at http://www.openhandsetalliance.org.cn
Building...
Build Ok.
Into newrom folder no system.img file when go to create image. Just unpacked files and folders without system.img.
After that, system.img is corectly created but have 2GB.
Click to expand...
Click to collapse
Please attatch a screencap before and after you run the mkfs.yaffs2 command. Please be sure that the target directy is clearly visible.
There is the problem...
First picture is when unyaffs and second is when create image file after mkfs.yaffs2.
FileFixer said:
There is the problem...
First picture is when unyaffs and second is when create image file after mkfs.yaffs2.
Click to expand...
Click to collapse
I don't think your output path should be in the same folder you're trying to make an image from. That's the problem
Fix that and i'm positive it will work. Hope that helps.
I tried this method and system.img is created in new folder but this sistem.img no contains folders and files from /newrom folder. It contain a files from my Ubuntu system folder?!
I am confused...
ok have system.img in newrom folder in Desktop.
1.open terminal
2.cd Desktop/newrom
3.unyaffs system.img
4.now go remove the system.img file from your newrom directory
5.if you didn't close terminal type "cd.." to change path back to Desktop
6.mkfsyaffs newrom/ system.img
Sent from my HTC HD2 using XDA App
Thanks... Now it works perfect.
Now i go to write Begginerr guide for yaffs and unyaffs. It is very simple...
Best regards.
FileFixer
I've been working on a custom rom with android kitchen and I want to get the system.img and boot.img.But the system.img seems to be extracted and the boot.img isn't.How do I get the system.img?Can I make .img file with power archiver or something?
fdespotovski said:
I've been working on a custom rom with android kitchen and I want to get the system.img and boot.img.But the system.img seems to be extracted and the boot.img isn't.How do I get the system.img?Can I make .img file with power archiver or something?
Click to expand...
Click to collapse
If your PC using linux system,I recommend you to use Virtual Box.
If U using windows system,you must configuration Java environment first,and then install a software who name is Cygwin,You can use it to extract the system.img and boot.img.
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
I want to custom kernel without magisk.
So i tried to unpack boot.img in order to modify kernel in boot.img.
But, i couldn't unpack boot.img with any other unpack tool like Android image kitchen.
Common problem is about ramdisk.
i guess common unpack tools can't unpack pie 9.0 boot.img.
so i used different ways flashing other rom's boot.img because of using recent custom kernel. However, it is just temporary action.
do you know any other ways to unpack boot.img?
Letmeseeforest said:
I want to custom kernel without magisk.
So i tried to unpack boot.img in order to modify kernel in boot.img.
But, i couldn't unpack boot.img with any other unpack tool like Android image kitchen.
Common problem is about ramdisk.
i guess common unpack tools can't unpack pie 9.0 boot.img.
so i used different ways flashing other rom's boot.img because of using recent custom kernel. However, it is just temporary action.
do you know any other ways to unpack boot.img?
Click to expand...
Click to collapse
You can unpack any boot image if you have the right tools. If the problem is with unpacking the ramdisk, that would be because you are trying to use the wrong tool to decompress it. Open the ramdisk image with an hex editor, and post the values of the first 4 bytes. And then tell us which tool you are trying to use to decompress it.
Why ramdisk is empty?
Bro I have redmi note 7 pro
when I unpack boot.IMG , ramdisk folder is always empty
Why ?
is there something that I missing?