I am interested to know what tools are available to do a "diff" ( http://unixhelp.ed.ac.uk/CGI/man-cgi?diff ) between ROMs in Android and, if possible, even against the a nandorid backup or some other method to get the file on the phone.
I expect that it would be possible to to extract the content of the ROM on two different folder and then running a opendiff or some other tools (ex: http://meldmerge.org/ ) on the two folder.
I am trying to see what executable and what script changed between a stock ROM and what I have currently running on my phone or other ROMs available here.
Thank you in advance!
Related
Hi,
Following this thread: http://forum.xda-developers.com/showthread.php?t=310287 I created a dump directory for a WM6 image. Inside the SYS directories are a number of subdirectories. Some of these subdirectories have familiar names (e.g. calendar.exe). Using calendar.exe as an example, there are 5 files: imageinfo.bin, imageinfo.txt, S000, S001, and S002. Here are my questions:
1. What are these 5 files?
2. What tool would I use to put the folder together to create a single executable?
Sorry for the noob questions but I can't find the answer on the forums!!
OK, after trying out all of the tools in one of the bundles, I found the answer to the second question:
2. Within someone's kitchen tools (I don't remember which one I downloaded) was a file called recmod.exe. Run it with the folder as a parameter and it will put the exe together.
I still don't have the answer as to what those 5 files are though.
My terms may be off base but I'll try to explain what these files are as I understand it (and hopefully not look stupid in the meantime as I'm also trying to explain it in layman's terms).
Many core files are constructed like this so that they are optimized in the Rom to make them run more efficiently on our devices.
Hi guys, I was wondering how you would go about personalizing ROMs for your own use. Nothing code-wise, but installed programs and such. Opening up the zip files of downloaded ROMs I see the apk files and the system apk files - is it really as easy as just removing those you don't want and plotting in the ones that you do?
If this rom is from the same board as you, can say so.
But, .. you still need to run a linux terminal the code to sign the package that you previously made with same special files..
Just the search tools and you'll find it!
...You can easily too start porting rom's too...
Is anyone here familiar with flashing WM roms using DMTool? I have a device (I can't say which, sorry), that uses this utility for flashing ROMS with a .hex extension (3 files, for radio, OS and ExtRom), and I'm wanting to see if I can update the OS build (comes with WM 6.5 build 21840, which is OLD!).
It's not exactly an uncomplicated process to flash this thing, but I'm fully familiar with it; I just have I've no idea how building the OS .hex file differs from the more common .bin or .nbh files use with EUU/RUU flashing utilities.
Google isn't being very helpful either...
Hey guys, I'm trying to tinker with the recently-released Telstra-Branded Froyo ROM so I can check on some of the data inside and modify T-Mod to suit, but I've come across two very strange problems:
1: Extracting the update form the RUU gives me naught but a .img file which I have no clue how to open (I know it's a filesystem image, but I haven't been able to find tools to open it)
2: The OTA version of the update, while easily viewable, seems to use a .p file based patching system that I have never seen before.
If anyone can help me with these two problems by providing me with either the tools to decompile the RUU into something I can actually look at, such as tools for android's .img filesystem format, or a decrypted version of this ROM, it would be greatly appreciated.
EDIT: Nevermind, I found a copy of unYAFFS, figured it all out. just had to figure out what the filesystem on the RUU was.
Edit: I see you found it..
I know you're sorted now Muskie, but using dsixda's kitchen is also a useful tool.
http://forum.xda-developers.com/showthread.php?t=633246
Run the ruu until the menu comes up, go to your temp folder and copy the rom.zip and whack it in the kitchen.
Ben
Hi Guys
I need some basic help/understanding about Android ROM modification.
In particular for an Android MX TV Box - but the questions is generic and applies to any ROM I guess.
The Rom im flashing has the following files (and works perfectly):
factory_update_param.aml
hd18d_mx4.zip
recovery.img
I am able to successfully restore my box with this image (so I know that the image is working fine).
Within the hd18d_mx4.zip there is:
Directotories: data, META-INF, recovery, system
files: boot.img, bootloaded.img, logo.img
I tried to do a very basic step of deleting a single system.apk file from the system/app folder (no other changes) and I am unable to flash this firmware.
Any ides - what am i doing wrong?? It seems like i cant make any modifications to the zip file or there are problems.
I tried using dsixda Rom kitchen, and even if put rom in working directory, and then immediately
Please help - this is driving me mad!! Aaarrghghg