anyone knows wich files are relevant when porting an SDK image to our loved O2x phones?
boot.img for sure but what about lge-ril.so for eg.?
and which files are device dependant for hardware lib's etc.?
Files i know we need:
boot.img
lge-ril.so
libEGL_tegra.so
libGLESv1_CM_tegra.so
libGLESv2_tegra.so
gps.p990.so
gralloc.tegra.so
lights.p990.so
overlay.tegra.so
sensors.tegra.so
kernel-modules
libnv*.so
Related
Hi,
I've extracted some ROMs and built my owns and I realized that in the newer ROMs a lot of .dsm files are present. I think these can be deleted just as the .rgu files can, because as far as I have tried it, they are only necessary for building the ROM from its parts but now for assembling/running it. Would save some space...
Regards,
Stefan
Hi,
I have a ROM, for example Enomther's. and I also have the arabic language libs. how can I integrate the arabic libs into the ROM's zip file so I don't have to flash another zip for arabic libs? I have attached the arabic libs.
Bump! anyone?
Come on, what kind of answer do you expect?
Here's the answer: you need to substitute the files in the original ROM zip and resign it - that's it.
Now you're going to ask, how to do it, because you have no clue - and the explanation is a lot of work to try and put in one post, and setting up signing applications involves installing Java SDK and some knowledge. If you're asking the question you're asking - it seems like you're far from being skilled enough in Android depths to do what you're asking to do, and that's why you see no answer. After all, if you'd want to do it - you'd have to search anyway, Google "sign apk zip" and here you go, a lot of tutorials show up. And if you didn't search and posted instead - it speaks for itself.
By the way, there's no good reason to integrate the libs into a standard ROM, moreover - it's a bad idea. ROMs tend to be updated, and the work that needs to be done setting up the environment for signing APKs and ZIPs is way more than flashing one update right after updating the ROM to a newer version. And ROMs are updated quite often.
Yeah i'm not skilled. I'm trying to learn... I am trying to make my own customized ROM for my country's users. And I didn't mean editing ROM files, I was saying how to push the lib into the ROM zip so people don't have to flash the arabic zip lib when they flash my customized ROM. So I hope you haven't missunderstood my question...
Ah, I see, you want to customize and share the ROM. In that case, you have to have the setup I'm talking about. The update.zip contains folders and files, which directly replace the files in the same folders in ROM, so if you have a ROM zip - you need to replace those files. The easiest way would be just extracting your update.zip, opening a ROM zip in 7zip / WinZip / WinRar / etc, putting those extracted files from update.zip in the right place into ROM zip by drag-and-drop, and then resigning the ROM file.
Please do some googling as to how to sign ZIP and APK files. There are some pretty good tutorials.
I have done that before, and I replaced the lib file with the ROM default lib. it's libskia.so, but I think because I didn't know I have to sign it it gave me an error while flashing through recovery. so after I replace the lib I have to re-compress the file and then sign the zip right?
You don't have to re-compress if you replace the file without decompressing the original ROM archive, by dragging-and-dropping the file into the archive.
And yes, you have to re-sign the ZIP after any changes you make to anything inside it.
hey guys.. i been looking around everywhere to try and get a good explanation of the files inside the rom.zip... like what the files are in the META-INF? and what are all the files inside the system folder? how do i know what to change and what not to change.. lol sorry but if anyone could possibly give me a more in depth explanation i would appreciate it greatly!!!
i dont have answer but i would also like to know this... since im just trying to learn how be a dev...
lol seems no one can help us... but this did help a little... http://forum.androidcentral.com/hacking/6037-general-rom-faq.html
Hi
The files in META-INF are just that, meta files they contain information about the files that are part of the rom.. specifically CERT.* and MANIFEST.MF contain the SHA1 hash of each file in the rom when you flash the rom your recovery environment hashes each file and checks it against the manifest. These files are created during the signing process.
META-INF/com/google/android/updater-script tells the recovery environment what to actually do. such as format /system then extract system to /system on the phone, set permissions for each file and the correct kernel to your boot.img then reflash it
the files in /system are the actual operating system and are in a UNIX-ish layout
executable's in bin & xbin, system apks in app, configuration files in etc, libraries in lib, ringtones and bootanim in media
rattking said:
Hi
The files in META-INF are just that, meta files they contain information about the files that are part of the rom.. specifically CERT.* and MANIFEST.MF contain the SHA1 hash of each file in the rom when you flash the rom your recovery environment hashes each file and checks it against the manifest. These files are created during the signing process.
META-INF/com/google/android/updater-script tells the recovery environment what to actually do. such as format /system then extract system to /system on the phone, set permissions for each file and the correct kernel to your boot.img then reflash it
the files in /system are the actual operating system and are in a UNIX-ish layout
executable's in bin & xbin, system apks in app, configuration files in etc, libraries in lib, ringtones and bootanim in media
Click to expand...
Click to collapse
wow rattking thank you very much!! that was the best description anyone has ever given me!!! lol that was very helpful!! is there a place where you learn this from? or did you just figure it out as you went..?
Hello!
I'm trying get some information about the .wdb format, if anyone know something I really like to know about.
For example, the kdb is a crypted cab file, who have inside some other files.
Maybe a .dz and a .dll or a .dll and a .wdb, is there a "third option"?
I heard about CDMA and 3GQTC, it's how this files are "packed"? (in kdz)
I see that KP500 got a .wbd extractor, then, if we extract it, we got 5 different files *.dfat, *.fls and others...
So, what can we do with that files extracted from .wdb, what we won with this?
Can we create custom roms or something like that?
I think this concept work for all the LGE cellphones or almost everyone, right?
Thanks.
[]'s
You could use [1]TrID to see if it can tell something
[1]http://mark0.net/soft-trid-e.html
Probably inside the wdb there's the files that compose the rom, like the dz which contains the recovery.img, boot.img and so on. LG seems to have changed the decompress process as the KP500 lg utils cant decompress the wdb files. Maybe with the files we could create a new kdz and flash it, just like this tutorial
http://code.google.com/p/arenoid/wiki/KDZExtractPack
It's an encrypted archive that stores the fls file and bin files in multiple parts. It seems the decrypting function is inside the dll that's extracted from the kdz.
Answering my own question.
WDB is a container format, with several pieces of zlib streams, each representing a file, but encrypted.
Like a zip file
Hello Everybody
I want to make a Custom ROM from three ROM's.
1) The most folder in /System I know, but the bin and the etc, I don't know.
2) I mix the files from a stock based and a cm based ROM. Which folder determine if the ROM ist cm or stock based?
3) How I can open the files in the bin and the framework folder?
Regards heubergen1
heubergen said:
Hello Everybody
I want to make a Custom ROM from three ROM's.
1) The most folder in /System I know, but the bin and the etc, I don't know.
2) I mix the files from a stock based and a cm based ROM. Which folder determine if the ROM ist cm or stock based?
3) How I can open the files in the bin and the framework folder?
Regards heubergen1
Click to expand...
Click to collapse
1. /bin and /etc are located in the /system subdirectories on most roms.
2. Not sure what you are doing here. With the exception of "some" files, most CM files cannot be mixed together.
3. You must decompile the files in the framework folder. Like framework-res.apk, services.jar, android.policy.jar before you can edit the xml files. You need to get apktool to do this.
MD
Thanks for your Answer.
1) I mean, what is there? What lose Android when I delete it? (e.g: In the system/lib folder are files there use many Apps and for the Performence and a clearly Code that will outsource.
2) I extract the ZIP for X-Gamer, CM7.2 and the Smart Xperia ROM. Then I take e.g. the Bluetooth files from CM, the charging driver from X-Gamer and the libary for share from the Smart Xperia ROM. Which files I must take from the same source? I hope it's no understandable.
Do NOT delete etc and bin folders
You can read the 'Introductionary Zip tweaking' guide in XDA-U.I have given a brief description about them there which you might found to be useful
printf("random signature because I have got nothing else in my mind right now");
Thanks for your answer.
Have somebody one for my second Question?