So, i've decompiled my boot.img (from F320K) and i've now a zImage file and no Ramdisk folder too, so i suppose ramdisk files are inside zImage file.
Ho knows a right method to decompile this zImage file ? For G2 sure .
wolfgart said:
So, i've decompiled my boot.img (from F320K) and i've now a zImage file and no Ramdisk folder too, so i suppose ramdisk files are inside zImage file.
Ho knows a right method to decompile this zImage file ? For G2 sure .
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=761893
http://forum.xda-developers.com/showthread.php?t=1659584
http://forum.xda-developers.com/showthread.php?t=633246
hope it can help
Thank you but i've used all three method but they are not useful to decompile G2 ' s zImage
Sent from my iPhone using Tapatalk
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'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.
Hello
can any one tell me how i can extract a rom so i can gate some apk that my original rom use to have.
thank you
unzip with winrar
system>app> apk files here
Questions to general section please. Written in forum rules.
Sent from my u8800 using XDA App
Thank you oguzhan mobile
How to extract the update.app (stock rom file)?
andreasha said:
How to extract the update.app (stock rom file)?
Click to expand...
Click to collapse
The attached should be all you need. split_updata.pl will extract the system image which you can then mount directly. splitfile.c will extract the mbn files and boot.img. Use abootimg to extract the kernel and initrd and then cpio to get the root fs from the initrd. Obviously you will want to use a linux box for this.
dzo said:
The attached should be all you need. split_updata.pl will extract the system image which you can then mount directly. splitfile.c will extract the mbn files and boot.img. Use abootimg to extract the kernel and initrd and then cpio to get the root fs from the initrd. Obviously you will want to use a linux box for this.
Click to expand...
Click to collapse
Thanks mate, really nice instructions!
Hello i have compiled stock kernel from lg sources and created the zImage file in arch/arm/boot folder using 4.6 google toolchain.I want to know how to make it flashable as zip file.I have tried anykernel tool without success :/ Any help appreciated!
I have some original C code, which I have compiled successfully, and like to put on my phone, SM-N900P. I downloaded a copy of stock firmware and used unmkbootimg to unpack the boot.img. What do I do from here on? I have searched online and this site. I believe I have to put my files in the ramdisk directory. What I do not know is what files go in there? Can I put .img files in there? Is there a specific order in which directory to use within the ramdisk? I read someone's post instructing me to put the .ko files in ramdisk/lib/modules directory. But the ramdisk directory I have does not have a /lib directory. Should I create one? I only ask because each phone seems to have a different setup. I basically have a zImage, dt.img, and a couple of other img files.
Even if you can not help, I appreciate if you point me to relevant useful information.
Thanks
sansari123 said:
I have some original C code, which I have compiled successfully, and like to put on my phone, SM-N900P. I downloaded a copy of stock firmware and used unmkbootimg to unpack the boot.img. What do I do from here on? I have searched online and this site. I believe I have to put my files in the ramdisk directory. What I do not know is what files go in there? Can I put .img files in there? Is there a specific order in which directory to use within the ramdisk? I read someone's post instructing me to put the .ko files in ramdisk/lib/modules directory. But the ramdisk directory I have does not have a /lib directory. Should I create one? I only ask because each phone seems to have a different setup. I basically have a zImage, dt.img, and a couple of other img files.
Even if you can not help, I appreciate if you point me to relevant useful information.
Thanks
Click to expand...
Click to collapse
boot.img contain: ramdisk, zImage (kernel compressed with modules), dtb (device tree binary) and some time have name dt.img.
When you compile kernel from source, you will get zImage and dt.img (if you use dtbTool to merge all device tree rev). Use xiaolu's unmkbootimg to extract stock kernel to get ramdisk and modify it, replace zImage and dt.img then repack it to become boot.img and ready to flash it.
You should create thread in Q&A box
hiepgia said:
boot.img contain: ramdisk, zImage (kernel compressed with modules), dtb (device tree binary) and some time have name dt.img.
When you compile kernel from source, you will get zImage and dt.img (if you use dtbTool to merge all device tree rev). Use xiaolu's unmkbootimg to extract stock kernel to get ramdisk and modify it, replace zImage and dt.img then repack it to become boot.img and ready to flash it.
You should create thread in Q&A box
Click to expand...
Click to collapse
Thanks. I'll move to Q&A