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.
Related
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
hey guys since i was getting so many requests to make custom bootscreens/bootlogo, and lots of ppl asking me how to do this i am making this how to...
it took some time for me to get all this info and tools in one place and make it easy to use...
[ INTRO ]
this little how-to/tutorial will cover points on how to convert between image files and (static) bootscreen/bootlogo files (initlogo.rle/logo.rle)
THIS WILL NOT COVER INFO ON HOW TO INTEGRATE IT IN CUSTOM boot.img, i will add this later cause it requires different tools
initlogo.rle/logo.rle are image files which are in the integrated ramdisk in custom kernel boot.img
these .rle files are shown during booting of the custom kernel (boot.img)
if u want to remove showing of these images then just delete the initlogo.rle/logo.rle from the ramdisk
if u want to change it to the image that u want then follow this tutorial
after creating the .rle files u will need to rename the files to initlogo.rle / logo.rle and place it within extracted ramdisk folder then repack the ramdisk and then repack it with kernel (zimage) using proper boot address and specific command line parameters
[ CREDITS ]
makers of 5652rgb, to565 for freely providing the sources!
ImageMagick for the brilliant convert.exe tool
me for creating the cygwin binaries and batch files & making it little simple to use
[ REQUIREMENTS ]
windows PC (u can find compatible linux tools if u search online)
this package
correct resolution images (check post #2 for details)
[ WHATS INSIDE? ]
the package i have provided has:
precompiled cygwin binaries for
5652rgb
to565
convert.exe from ImageMagick-6.7.0-Q16-windows
all required dlls for standalone installations
easy to use batch files i made
convert_image_to_rle.bat
convert_rle_to_image.bat
[ HOW TO USE? ]
Converting any image to rle file
open command prompt and browse to folder with those bat files
execute:
Code:
convert_image_to_rle.bat <path_to_image_file>
the <path_to_image_file>.raw file and <path_to_image_file>.rle file will be created at the same location as <path_to_image_file>
Converting any rle to image file
open command prompt and browse to folder with those bat files
execute:
Code:
convert_rle_to_image.bat <path_to_rle_file>
the <path_to_rle_file>.raw file and <path_to_rle_file>.png file will be created at the same location as <path_to_rle_file>
[ ADDITIONAL INFO ]
the batch files i have made are specific to X10 screen resolution (480x854) if u need to use it for another device just edit the convert_rle_to_image.bat file and changed this like
Code:
[user=220077]@bin[/user]\convert -depth 8 -size 480x854 rgb:%1.raw %1.png
[ DOWNLOAD LINK ]
boot_screen_logo_creation_package.rar
[ REFERENCES ]
http://forum.xda-developers.com/showpost.php?p=6775233&postcount=5
http://www.androidtablets.net/forum...-before-animated-boot-animation.html#post1895
http://android.git.kernel.org/?p=platform/build.git;a=tree;f=tools/rgb2565
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images <<< has info on how to pack/unpack boot.img files
aZuZu has uploaded newer tools!!!
Chumby_666 said:
new version of custom boot image toolkit is up!
minor fixes ...
added image to android logo & android logo to image ( external tools ) ( cygwin again! god damn! )
working on new ramdisk handle procedure ... soon will be fixed
thanks DooMLoRD for finding tools
Click to expand...
Click to collapse
get them here: http://forum.xda-developers.com/showthread.php?t=1090217
[ INFO ON SCREEN RESOLUTIONS ]
the resolution of the image to use depends on ur the capabilities of ur device
following is a list of the resolutions
QVGA (320×240)
WQVGA (432×240)
HVGA (480×320)
VGA (640×480)
WVGA (800×480)
FWVGA (854×480)
Very useful!
Thank a lot.
& this is WHAT i want!
Great work bro!
Cheers
SX,
Just what I needed..
Many thanks, no need to pester you any more for bootscreens, but many thanks for the ones you provided t me
For some reason it isn't working on my computer, I have no clue why .Running everything exact ,but it could be my phone .Does any one have some spare time to whip one up for me? Any help would be greatly appriciated
Does not work it creates a rle file on 0.00kb
Sent from my X8 using XDA App
getting a bit farther but it tries to take my image to rle but it says it can't find the file
any chance there could be a bit more noobish instructions to follow or is there any way to set it up like the moto devices could with a logo.bin file
pouxonu said:
getting a bit farther but it tries to take my image to rle but it says it can't find the file
any chance there could be a bit more noobish instructions to follow or is there any way to set it up like the moto devices could with a logo.bin file
Click to expand...
Click to collapse
make sure that there are no spaces in the path to the image file... best way is to place the image file in the same folder as the batch files
for exapmle how should this be typed. I have the set up in my c drive near my sdk
convert_image_to_rle.bat
Program Files_Android_boot_screen_logo_creation_package
does all that need to be together with underscores? And do I need the name of the image?
i found draging and droping the logo.rle on top of "convert_rle_to_image.bat" did the trick for me. before it was giving some errors.
jus shared my find.
i'm making a bootscreen, anyone know what's the name of xda developer's font or can share it, please?
ayyu3m said:
i found draging and droping the logo.rle on top of "convert_rle_to_image.bat" did the trick for me. before it was giving some errors.
jus shared my find.
Click to expand...
Click to collapse
i did a drag and drop and it seems to have worked, now i'm totally lost in what to do next
Doomlord... you are a miracle worker XD even when I'm not looking for something for my X10 you seem to solve all my problems XD
Hi DooM bro,
How to cpio.gz the ramdisk folder after editing it?
I tried the azuzu tool but i get error.
Any other way?
Linux, windows, anything any other script? Or can u gz the ramdisk for me?
weaponXandroid said:
Hi Doom bro,
How to cpio.gz the ramdisk folder after editing it?
I tried the azuzu tool but i get error.
Any other way?
Linux, windows, anything any other script? Or can u gz the ramdisk for me?
Click to expand...
Click to collapse
u need to use linux
go to the folder which has the ramdisk files (init,etc)
give this command:
Code:
find . | cpio -o -H newc | gzip > ../ramdisk.cpio.gz
can you please divert me a link how to import this rle file into phone/tablet ?
thanks
indigo_blue said:
can you please divert me a link how to import this rle file into phone/tablet ?
thanks
Click to expand...
Click to collapse
it depends from device to device...
some devices have bootlogo in boot.img (ramdisk) other have a seperate partition to dump this splash image
DooMLoRD said:
it depends from device to device...
some devices have bootlogo in boot.img (ramdisk) other have a seperate partition to dump this splash image
Click to expand...
Click to collapse
Well, I managed to make .rle file... So, how can I add it into DooMLoRD kernel?
I am using ARC S...
Ninolina said:
Well, I managed to make .rle file... So, how can I add it into DooMLoRD kernel?
I am using ARC S...
Click to expand...
Click to collapse
u need to repack ramdisk and then repack it zImage to get boot.img (using correct mkbootimg arguments)
there was a thread somewhere by SE on how to make kernels for Xperia 2011 devices... they have provided info on how to repack ramdisk and the correct mkbootimg arguments...
DooMLoRD said:
u need to repack ramdisk and then repack it zImage to get boot.img (using correct mkbootimg arguments)
there was a thread somewhere by SE on how to make kernels for Xperia 2011 devices... they have provided info on how to repack ramdisk and the correct mkbootimg arguments...
Click to expand...
Click to collapse
Thank you very much for answering me, but I am afraid it wont help me much... I dont want to make a Kernel, I only want to change the SplashScreen... On HTC Desire it was easy to do that (there is a Tool for that) and with ARC this and everything else is so much complicated... I also see that there is not much support for this device and so little number of people is willing to help...
Thank you one more time... I hope there will be easier ways to do this and other stuff which are standard on other devices...
Just one more question... Is it easier just to remove the SplashScreen that is now in DooMKrenel? I will be satisfied with that too...
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!
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
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