ok here is my question..
im trying to extract the system.img files to restore some of the original files i changed.
here is the things i want to know in a list
1, Which tool is used to extract those IMG files? guide please. if you do need to compile it please post guide on how to compile as well?
2, how to repack the files into readable Img files which we can use to fastboot flash system with?
3, the shutdown.zip and downanimation.zip what are the requirements? i have sucessfully made a custom bootanimation.zip but failed the downanimation and shutdown. the bootanimation works when i made zip file with store only attributes "no compression", but the other 2 wont work either way..
if i can get this information i would make a general thread about DHD with all the information so it would be easier for anyone to find out all about xda and the development for DHD
example, Radio/Eng S-Off CID-1111111 simunlock, adb commands/tools/guide, cygwin/unyaffs GIMP etc including graphical mods and specific how to's.
please help me out this might reward the newbies alot saving loads of precious time searching.. just like me
rofl edited to change adb to fastboot. sry my bad. stupid typo ;x
Related
I'm trying to figure out how to unpack and repack the evo's boot image. I found the "HOWTO: Unpack, Edit, and Repack Boot Images" thread in another forum using the search function but when I tried to use the scripts to unpack the boot.img file I received an error as follows:
Found a secondary file after the ramdisk image. According to the spec (mkbootimg.h) this file can exist, but this script is not designed to deal with this scenario.
The HOWTO thread I found mentioned that this was likely a second stage loader but indicated that it has not been seen on any system to date. This second stage loader had apparently only been defined in the mkbootimg.h file but not implemented as of the time this how to was written.
Can anyone provide a link to instructions on how to extract and repack the boot.img for the EVO? I'd like to make a few changes to the default.prop in the ramdisk of the default boot.img file and instructions would be greatly appreciated.
I use dsixda's kitchen
http://forum.xda-developers.com/showthread.php?t=633246
that allowed me to unpack it. I remember the error you speak of but I forget what script I was using
elegantai said:
I use dsixda's kitchen
http://forum.xda-developers.com/showthread.php?t=633246
that allowed me to unpack it. I remember the error you speak of but I forget what script I was using
Click to expand...
Click to collapse
This worked for me perfectly.
Thanks very much for the pointer!
hello everyone, I am posting to request some help needed to install a new splash screen. Now before people go posting other forum posts about how to do this, I will let you know i have spent several days looking for the information and i still need some answers.
A. does the image need to be 480x800 or 340X480? whats the difference if both work.
B. I want to use terminal emu. to do this and i found the command, and i know it has to be named splash1.img, now do i need a .txt file as well when the .img file is on the root of SDcard?
thank you for your help
The image does need to be 480x800 and you only nees the img file on you sdcard nothing else.
[sig]My mission is to hit 1000 posts by 23/05/2011[sig]
cjward23 said:
The image does need to be 480x800 and you only nees the img file on you sdcard nothing else.
[sig]My mission is to hit 1000 posts by 23/05/2011[sig]
Click to expand...
Click to collapse
thank you very much
This really should be in Q&A, and not even there. A search in Development would explain exactly how to create the splash1.img file using ffmpeg.
Anyone know how to edit the ramdisk inside the boot.img? Like for example: the boot image from the Particle Android Rom -- when you boot up your phone it says Samsung Galaxy Gio 5660
Is there some way to edit this to make it say 5660m? I believe i has something to do with the ramdisk folder that you extracted from the boot.img
EDIT-------
@UtmostMick0 The dsixda kitchen is not fully for the GIO. So you should expect some probs
----------
No,if you want to change it,you should change Gio.rle
Sent from my GT-S5660 using xda premium
czkwg8 said:
No,if you want to change it,you should change Gio.rle
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
Yup, try to search XDA for ''changing boot splash image''
I'm not in a position to help you out completely, but the others have been largely correct.
The boot.img file contains both the kernel and the ramdisk, there are scripts for both Windows and Linux to unpack and repack the boot.img files.
After that, you'll need to find a command line utility to convert the RLE (gio.rle) file into a RAW Run Length Encoded bitmap image that's going to be compatible with an image editing program of your choice.
Depending on the editing program used, if you want to do color, you may need to swap around your RGB channels in order to get correct results on the phone.
Let me know if you can't find the programs and I'll try to dig them out for you. But you should be able to find them somewhere on XDA.
kewl , someone else is playing with this to atm , lolz , i have used the dsixda kitchen to unpack my boot.img and got the GIO.rle file out of it , my problem is when i put replacement GIO.rle into the boot.img and repack it the wifi doesnt work :-( , any ideas ?
CM 7.2
I cannot find a method in Linux or Windows that will allow me to access the files in the system.img partition image from:
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350_signed.exe
I have never had a problem "unpacking" system.img files from other HTC phones using unyaffs or even in Windows with WinImage for EXT2/3/4 partitions.
Obviously many Devs have had success with the HOX system.img! Could someone please tell me what file system the system partition uses AND/OR reveal the correct approach to accessing the files within the img?
I presume the partition formats are identical in:
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.28.728.9_Radio_1.1204.103.14_release_256493_signed.exe
...so I suppose there's no point in making an attempt with its system.img either!
Any help will be greatly appreciated!!
Thanks in advance.
BTW: I'm not one who asks for assistance as his 1st move.
I have been searching for resolution to this problem for @least a week!
Using appropriate keywords the best I have come up with is either others in this same predicament or suggested remedies which are not effective.
The overall picture I have got is that those with the solution seem reluctant to share the knowledge, which I find strange in development communities.
if you want just access to files inside the img, in windows use this jar attached to convert it to ext4 and then mount with DiskInternals Linux Reader.
or in linux use this tool to unpack.
http://forum.xda-developers.com/showthread.php?p=28837507#post28837507
don't even try to repack it will not work.
if you know how it posible to repack files to this img format please let me know.
Thanks heaps avicohh!
I solved the problem only a few hours before your post came in.
I used a slightly different approach through linux but basically same process & result.
If you follow this:
http://forum.xda-developers.com/showthread.php?t=1081239
you'll be able to unpack AND repack but it's done in linux.
I used Ubuntu 12.04 LTS (64bit) to compile & use the ext4_utils in the thread above.
Since you were so kind to answer my query please feel free to PM me if i can help you!! My use of the forum is sometimes sporadic though, unfortunately.
EDIT: Sorry, just realised we both had the same thread! So it doesn't work for repacking?? I'll see if I can find something that works.
Obviously something does but there's not as much free sharing of really useful stuff as I would have expected with this kind of thing.
Yap.. is the same thread.
probably the odin (samsung) img and the stock htc img they not exactly the same format.
i seraching after sulution to this thing because i'm trying to make custom rom to be able to flash on device with stock rom/locked bootloader from the stock recovery like the ruu firmwares.
in order to create a flashable bootloader.zip we need to be able to extract the bootloader-flo-flo.4.04.img file all the img utilities I tried to unpack that file give a bunch or errors
can anyone see if they are able to unpack that file with imgtool or imgRePackerRK or other?
If anyone can try and unpack the bootloader-flo-flo.4.04.img file I am not sure why I keep getting bad file descriptor errors when trying to unpack it using imgtool
with that unpacked it should be easy to make a flashable bootloader, and there are a bunch of people all over that need this that either do not have access to a machine or like myself the USB port is not working at all on the device.
I second this!
Please!
Pleeeeeease!!!!
OPO Yeauh!!!
Agreed! I currently donr have a computer so i cant update rhe bootloader
The recovery flashable bootloader can now be downloaded from the link posted in this thread http://forum.xda-developers.com/nex...shable-factory-image-zips-android-5-t2939599/
Be sure to thank @eksasol I bugged him so much I feel really bad now, awesome work!