I have been working on rom development for LG Quantum. I have managed to extract the rom parts and from that, I have a "flash.bin" file which has (contains??) the OS.nb file. The only problem with it is that the flash.bin file has a "RA000F" header in it. HTC Rom Editor opens flash.bin if I rename flash.bin to OS.nb, but crashes when I try to get at files within it. I have tried finding the D000F header within the flash.bin file and extracted OS.nb from there. HTC Rom Editor allows me to extract imgfs.bin from the OS.nb that came from the flash.bin file. If I use the OS.nb taken from flash.bin, I can modify and rebuild the OS.nb with any changes I make, but then I can't reintegrate the changed OS.nb back into flash.bin.
Are there any tools which allow me to work with files with the RA000F header in them? Also, is there any real information (documentation) available on the RA000F rom format? I can't seem to find any real documentation on it.
Can anyone help me?
Please send me link for your rom , i try dump it
WojtasXda said:
Please send me link for your rom , i try dump it
Click to expand...
Click to collapse
Dump with what?
anaheiim said:
Dump with what?
Click to expand...
Click to collapse
Flash.bin from first post
Related
While I was cooking my own rom, I dumped the Stock Rom 1.90.485.3 which came preloaded on my TP which I bouaght in egypt.
I noticed a new cab file which was not included with any other rom I dumped to use in the kithcen.
This file is PT_DDI.CAB which is located in the OperatorPkg_PT folder in the OEM Folder and when extracted includes a New DDI.dll file.
I have searched for the DDI.dll file in all the stock roms and never found it, Only found a DDI.dll folder under Temp\Dump_XIP folder and it does not contain the DLL file only and which gets deleted when we start cooking the rom.
This rasis several questions
-Does this mean that the DDI.dll file is missing?
-Do we cook the rom without the DDI.dll file?
All experts please investigate the cab file included, this may lead to improved graphics quality for Raphael.
I have attached other drivers cab files also included in the rom
Thanks and best regards
As you've said, the ddi.dll is located in XIP, which is another storage area in the ROM that typical ROM kitchens don't modify without extra steps.
So the ddi.dll isn't missing, but yes you sort of cook without it (the XIP stays as-is in most kitchens without modification)
However this .dll may be different, let's take a look
Da_G said:
As you've said, the ddi.dll is located in XIP, which is another storage area in the ROM that typical ROM kitchens don't modify without extra steps.
So the ddi.dll isn't missing, but yes you sort of cook without it (the XIP stays as-is in most kitchens without modification)
However this .dll may be different, let's take a look
Click to expand...
Click to collapse
No, The DDI.dll Folder does not have a DDI.dll, I have attached the Folder for you to look at.
Best regard
Correct, that is a module. This is a format sometimes used to store files in ROM, it is quicker for the device to access these modules than it would be if the .dll was stored as a file. So yes, this folder does not have a ddi.dll, but, the device 'sees' this folder as ddi.dll and it functions as such.
Da_G said:
Correct, that is a module. This is a format sometimes used to store files in ROM, it is quicker for the device to access these modules than it would be if the .dll was stored as a file. So yes, this folder does not have a ddi.dll, but, the device 'sees' this folder as ddi.dll and it functions as such.
Click to expand...
Click to collapse
Now when you start cooking the BuildOS.ex deltes the temp folder and accrodengly also deletes the Dump_XIP folder which was in the temp folder.
Now if you do a search for the DDI.dll, It does not exist anymore.!!
What happend to DDI.dll module?
Regards
It is stored in the XIP, a seperate area of storage outside of the IMGFS, which is the area you are looking in when cooking. If you open the .nb or .nbh file in a hex editor, you can see the XIP area in the first section of the file.
For instance, using a hex editor, search for the string "ddi.dll" in the .nbh, you will locate it in the XIP section. Again this section is not normally modified during cooking, so when you see it disappear from the temp folder it has not been deleted from the ROM, only from the temporary copy extracted for use in the cooking process.
Furthermore, according to version info, the ddi.dll found in my Fuze XIP is ver. 1.95, as is the ddi.dll in the module you provided from your ROM. (open file S005 in notepad), while the ddi.dll provided in the .cab is 1.90. This doesn't mean it is better or worse, only different, have not looked into the differences.
shafez said:
Now when you start cooking the BuildOS.ex deltes the temp folder and accrodengly also deletes the Dump_XIP folder which was in the temp folder.
Now if you do a search for the DDI.dll, It does not exist anymore.!!
What happend to DDI.dll module?
Regards
Click to expand...
Click to collapse
Da_G are right, DDI.dll is part of XIP, and kitchen is not maked to modify the XIP, only use the XIP from the Shipped NBH file you put in BaseROM.
Anyway, seems your ROM have a CAB to update the DDI.dll file in the customizations, so perhaps a new version...
If you want modify/port the XIP start here http://forum.xda-developers.com/showthread.php?t=438676
Cheers
jcespi2005 said:
Da_G are right, DDI.dll is part of XIP, and kitchen is not maked to modify the XIP, only use the XIP from the Shipped NBH file you put in BaseROM.
Anyway, seems your ROM have a CAB to update the DDI.dll file in the customizations, so perhaps a new version...
If you want modify/port the XIP start here http://forum.xda-developers.com/showthread.php?t=438676
Cheers
Click to expand...
Click to collapse
All clear now,Thank you very much.
Best Regards
Thank you
Da_G said:
It is stored in the XIP, a seperate area of storage outside of the IMGFS, which is the area you are looking in when cooking. If you open the .nb or .nbh file in a hex editor, you can see the XIP area in the first section of the file.
For instance, using a hex editor, search for the string "ddi.dll" in the .nbh, you will locate it in the XIP section. Again this section is not normally modified during cooking, so when you see it disappear from the temp folder it has not been deleted from the ROM, only from the temporary copy extracted for use in the cooking process.
Furthermore, according to version info, the ddi.dll found in my Fuze XIP is ver. 1.95, as is the ddi.dll in the module you provided from your ROM. (open file S005 in notepad), while the ddi.dll provided in the .cab is 1.90. This doesn't mean it is better or worse, only different, have not looked into the differences.
Click to expand...
Click to collapse
Da_G
Forget to say thank you,please forgive me.
Thank you very much
Best Regards
Hey no worries, you got the answer and that's the important part No problemo.
How to Dump PDAViet ROMs. I dumped the ROm, but PackageTool does not work on it?
What is the Reason?
How to solve it?
SheikhAatif said:
How to Dump PDAViet ROMs. I dumped the ROm, but PackageTool does not work on it?
What is the Reason?
How to solve it?
Click to expand...
Click to collapse
PDAVIET ROM??? There are 2 reason.
1. The cooker is encrypt it so it undumpable.
2. The cooker remove all .rgu and .dsm file, rgu is the registry file, and dsm is contain location and group of file, PackageTool can't work without dsm & rgu file.
All PDAVIET ROM like that, so...search another ROM.
Imho , it may possible because encrypted file may we desrypted back, and diskimg.nb0 file (flash file) is still saving information about stucture original file (need may learn about it). Other way is to rearrange the files and directories result by dumper not rebuilt completely yet by BuildOS
If I have a *.apk that I download, is there anyway to backup/extract it?
The apk is really just a ZIP file. Try renaming the file to whatever.apk.zip and open using your favorite ZIP utility. You should be able to view all the contents. Resources (such as images) can be extracted. The java code is compiled into a .dex file so you can't view the raw code, but there are utilities (like this one) to decompile it: http://dedexer.sourceforge.net/
ghostfaced said:
The apk is really just a ZIP file. Try renaming the file to whatever.apk.zip and open using your favorite ZIP utility. You should be able to view all the contents. Resources (such as images) can be extracted. The java code is compiled into a .dex file so you can't view the raw code, but there are utilities (like this one) to decompile it: http://dedexer.sourceforge.net/
Click to expand...
Click to collapse
Right but how do I find the *.apk if I am downloading it off of the market?
apps are located in data/app/
There are also various apps in the market that will backup apps.
I use appmonster incedently.
7zip can extract and view contents of an apk without renaming.
backup and reinstalling apps....
view the first link in my signature.
I used MyBackup Pro to do a backup of my apps onto the sd card, then I used ASTRO file manager to navigate to /sdcard/rerware/MyBackup/AllAppsBackups where I found the file LastBackupApps.zip. I then used androzip or something similar to unzip that file and it contained the apk for every one of the apps I backed up.
how to extract .apk.p files
ghostfaced said:
The apk is really just a ZIP file. Try renaming the file to whatever.apk.zip and open using your favorite ZIP utility. You should be able to view all the contents. Resources (such as images) can be extracted. The java code is compiled into a .dex file so you can't view the raw code, but there are utilities (like this one) to decompile it: http://dedexer.sourceforge.net/
Click to expand...
Click to collapse
I have a zip file with .apk.p files in it which are exracted with package_extract_file in the updater script. Is there a way to manually extract these, since renaming to .zip doesn't help if I open them with any unzipper program?
Thanks
lxrose said:
I have a zip file with .apk.p files in it which are exracted with package_extract_file in the updater script. Is there a way to manually extract these, since renaming to .zip doesn't help if I open them with any unzipper program?
Thanks
Click to expand...
Click to collapse
I believe the files you are referring to - the files ending in ".p" - are "patch" files. They only appear in the OTA download .zip file, and they are worthless to you. They are not complete files, but just enough data to patch the corresponding 1.5 app .apk so that it turns into the 2.1 version.
If you want the complete .apk files which they correspond to, just download the Leak-V3 .zip file, extract the "system.img" file, and then unpack that file using the "unyaffs" utility (search for it, you'll find it at code.Google.com).
bftb0
bftb0 said:
I believe the files you are referring to - the files ending in ".p" - are "patch" files. They only appear in the OTA download .zip file, and they are worthless to you. They are not complete files, but just enough data to patch the corresponding 1.5 app .apk so that it turns into the 2.1 version.
If you want the complete .apk files which they correspond to, just download the Leak-V3 .zip file, extract the "system.img" file, and then unpack that file using the "unyaffs" utility (search for it, you'll find it at code.Google.com).
bftb0
Click to expand...
Click to collapse
Thanks for the info. I thought I can update the apk files manually, because from recovery it doesn't work (it is a rooted image, so signature not accepted) and there are some fixes in the new update that I wanted to give a chance.
Unable to install ddx1.14.jar in my HTC wildire
I hve downloaded dexeder.jar file in to my SD card. but i can't install it in my HTC wildfire...
it shows an error...
"ddx1.14.jar cannot be installed because critical information is missing from the application file (MIDlet-Name). Please contact the application provider for more information."
Help me Pls..... Thanks in advance.....
apk download
did you search for the apk online?
Hello,
someone knows if it possible (and how) extract Wallpapers from the firmware downloaded with NaviFirm?
Thanks
I haven't explored the sync features in Zune yet - are you sure you can't get them through that??
Otherwise, .esco files can be opened like a normal zip. Look for the big .esco firmware file (around ~370MB) and extract the .img file from it. If you can read the contents of the .img file, I reckon you could get them...
THanks Tj,
no works...I found the big .esco, extracted the boot.img...and that file is "empty"...no Winzip no winrar no Dtools can how what's inside it...I wanna extract a carrier's wallpaper... :/
alecksander said:
THanks Tj,
no works...I found the big .esco, extracted the boot.img...and that file is "empty"...no Winzip no winrar no Dtools can how what's inside it...I wanna extract a carrier's wallpaper... :/
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=20355160&postcount=4
thanks but...nothing...
It works...my mistake...i extracted the boot.img from the esco file and with OsBuilder i extracted all files...i cant find the pic i want...but thanks alot for help!
Ok i sux, I found what I want.
TYSM
Hi,
As the new ICS 4.0.3 seems to have gotten rid of the libraries required for call recording, I am willing to extract the relevant libraries from a 2.3.6 ROM, replace and give it a shot. I already have a few of them with me, for example Official DXKL3.
I need to extract the following 3 files -
system/lib/libaudiopolicy.so
system/lib/libaudioflinger.so
system/lib/libaudio.so
How can I extract these files from a ROM?
On you pc or on you phone click extract here. And will be exctracted about 6 files. Navigate to system app and find wht app you want. Copy and replace. I guess I understood right what you mean.
Get a utility program like 7Zip, IZarc, WinRar on your PC & open up the zip/tarfile & you can see the individual files & extract same.
However...
What you're attempting to do will not work. Different framework.
Points for thinking outside the box tho.
Thanks... Though when I use 7z, it only extracts zImage,factoryfs, etc., only a handful of files. I cannot see the individual files in the file system. Also 7z cannot extract these files anymore...
Ahh I think I was talking about already "cooked" ROM, and you guys are talking about the source? Sorry I am very new to the terminologies used. If that is the case I will check if I can find these files in the source tarball.
Try another program if 7Zip doesn't work. Try IZarc. I can see every file in the roms I have with it.
MistahBungle said:
Try another program if 7Zip doesn't work. Try IZarc. I can see every file in the roms I have with it.
Click to expand...
Click to collapse
I tried but still couldn't open XXLPQ ROM with IZarc. Thanks anyway...
hirak99 said:
Hi,
As the new ICS 4.0.3 seems to have gotten rid of the libraries required for call recording, I am willing to extract the relevant libraries from a 2.3.6 ROM, replace and give it a shot. I already have a few of them with me, for example Official DXKL3.
I need to extract the following 3 files -
system/lib/libaudiopolicy.so
system/lib/libaudioflinger.so
system/lib/libaudio.so
How can I extract these files from a ROM?
Click to expand...
Click to collapse
to open *.img file inside the rom download diskinternal linux reader and mount the img file inside the app.
tried and tested when i needed to copy a file from another rom.
Solution you find here :
h__p://sconcauteam.com/forum/index.php?threads/how-to-windows-extract-deodex-sign-and-zipalign-an-official-rom.1325/