PDA

View Full Version : Remove files from ROM


decebal
7th October 2003, 02:10 PM
How can I remove from the original ROM some files like T-Mobile, AIM ... etc. ?

I cooked up a 4.00.10 T-Mobile with GPRS monitor and batterypack but i want some more addons.

Can someone tell me what steps are required to remove from the ROM some files ?

Thanks,

Decebal

cruisin-thru
7th October 2003, 03:40 PM
ROM = Read Only Memory.

LumpiStefan
7th October 2003, 04:22 PM
But, i've we're able to add Programs to the ROM in the ROMkitchen, i think we're also able to remove programs.

Regards

Stefan

decebal
7th October 2003, 04:27 PM
ROM = Read Only Memory.

:cry:
obviously i do not deserve that

i was talking about the ROM image and since i've already succeded in putting into the ROM two apps i want to try something else.

so if anyone know how to remove at least T-mobile and AIM files from the image i'll be happy.

thanks,
Decebal

valheru
7th October 2003, 11:28 PM
I believe they are in an area not able to be modified.

cruisin-thru
7th October 2003, 11:56 PM
I was just quoting from that site, it does state that it cannot be erased, modified etc, no offence meant here. :roll:

jta
8th October 2003, 02:21 AM
The mkrom tools will allow you to 'unpack' a rom, i.e. extract all the files that are in it.

A rom, to the best of my understanding, has a 'native' or stock part to it, and then a series of XIP chains -- programs that are added into the free spaces of the rom.

I dont know what happens if you try to remove files from a rom that are part of the standard build...

Maybe the TMobile stuff is in a 'removeable' section of the ROM... there is also the 'operator' section... I am assuming that is a location that will give the 'operator' or creator of the rom space to put specialized programs, such as TMobiles phone apps, etc.

So, it seems that your best bet is to get the mkrom tools and read about how to extract/remove files/rebuild a rom.

Hey, it may even work!

J

Richjn
8th October 2003, 08:51 AM
You can rebuild a rom image from extracted files and leave some files out but Mkrom does not use compression and therefore the rom you end up with will probably be bigger than the rom you started with.

Richard

itsme
8th October 2003, 10:52 AM
If I am correct, an eeprom is something else than a flash-rom.
so the article at least states it incorrectly.
if it is flash, you should be able to modify it.

MrDollyMaker
8th October 2003, 07:20 PM
If I am correct, an eeprom is something else than a flash-rom.
so the article at least states it incorrectly.
if it is flash, you should be able to modify it.

Now, I do think that the real question is "How do we unlock the 'ROM' so that it can be modified being that it is an eeprom?"


Misterdollymaker

cgigate
9th October 2003, 03:58 AM
you need backup the ROM to *.nb1 or *.nbf file, than using tools to add/delete file to *.nb1 , write the new file back to XDA ROM. it is fun to add/delete file to your personized ROM!

david beckham
9th October 2003, 04:50 AM
you need backup the ROM to *.nb1 or *.nbf file, than using tools to add/delete file to *.nb1 , write the new file back to XDA ROM. it is fun to add/delete file to your personized ROM!

this is quite interesting...can you elaborate further?? I wish to learn more...

MrDollyMaker
9th October 2003, 05:43 AM
you need backup the ROM to *.nb1 or *.nbf file, than using tools to add/delete file to *.nb1 , write the new file back to XDA ROM. it is fun to add/delete file to your personized ROM!

Yes, please! I wish to learn more too! I am looking to remove the standard sounds and replace them with my own (using same names) as well as the boot image and desktop.

ntabikha
9th October 2003, 06:01 AM
yea, no kiddin, i'd like to know how too! :D
im sure its not impossible, 'they' did it the first time arround.
why not hacking it? and since its all at no charge (no profit) are we realy breaking any patents?

samohile
9th October 2003, 10:23 AM
I wanted to know if there is an easy :wink: way around, to put our own programs in the rom. xda-developers certainly can't put ezwap2.5, and the total commander appears to be older version, while new version is much better. There are some more freeware application I'd love to put in there :)

cgigate
9th October 2003, 03:20 PM
xda-developers already posted some tools to do job, such as MKROM ...

Timewolf
13th October 2003, 11:07 PM
you need backup the ROM to *.nb1 or *.nbf file, than using tools to add/delete file to *.nb1 , write the new file back to XDA ROM. it is fun to add/delete file to your personized ROM!

I'm interested too
How can i add/delete file from nb1 file?
Thanks

Fabio

JohnSmith
13th October 2003, 11:30 PM
I've used mkrom suite to do this (even for Smartphone2002). This are great tools.

Unfortunately it's not as easy as you might think. It's nearly impossible to build a ZERO-KNOWLEDGE ROM file explorer which can add or delete files "on the fly".

You will still have to look for valid gap's in the original rom where you can add a new XIP block.

All .exe and .dll files are "fixed up" that means they MUST run at THE fixed ROM position where they have been initially placed (execute in place). If you dump an exe or dll file you can't use it for other than disassembly to see how things work.

Removing files is a very hard task (they are splitted over the whole rom). And the resulting gap's are mostly not more than 10-16 kB. All you can do is to "hide" files (simply patch the directory entry).

So you see compression is not the real problem (see programers corner for a .bib file which can be used with romimage.exe - a Microsoft Tool to build XIP blocks, this tool supports compression)


John Smith

itsme
14th October 2003, 03:24 PM
only the kernel actually runs in the virtual memory area mapped to rom,
all the other XIP stuff runs from a virtual memory area mapped somewhere
in the top of each processes memory space.

( look at the 'real=' values in the output of dumprom )

so for all the other modules it should be possible to move them around
in rom a bit, I think you only need to keep the pagealignment the same.

JohnSmith
16th October 2003, 08:26 AM
Hi,

The virtual memory address is also fixed in the module. (That's why I've to rebuild all the stuff I want to copy from other roms).
Since all relocation info is gone the module can't run from another memory position. So the only thing you can do is to move it in it's own XIP section...

John