Related
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
ROM = Read Only Memory.
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
cruisin-thru said:
ROM = Read Only Memory.
Click to expand...
Click to collapse
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
I believe they are in an area not able to be modified.
I was just quoting from that site, it does state that it cannot be erased, modified etc, no offence meant here. :roll:
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
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
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.
XDA developer Itsme said:
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.
Click to expand...
Click to collapse
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
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!
cgigate said:
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!
Click to expand...
Click to collapse
this is quite interesting...can you elaborate further?? I wish to learn more...
cgigate said:
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!
Click to expand...
Click to collapse
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.
yea, no kiddin, i'd like to know how too!
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?
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
xda-developers already posted some tools to do job, such as MKROM ...
cgigate said:
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!
Click to expand...
Click to collapse
I'm interested too
How can i add/delete file from nb1 file?
Thanks
Fabio
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
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.
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
Hi there is a way to move "pim.vol" by register changes?
Re: There is way to move "pim.vol" location to Sto
zpdy said:
Hi there is a way to move "pim.vol" by register changes?
Click to expand...
Click to collapse
Hi I have asked this many occasions - in fact I would also like to get rid of the document and settings directory. It currently takes about 1.5mb on my device.
There is a program cleartemp that will remove contents of directories during reboot. However I am pretty sure that the files contained in the above directory and pim.vol are needed by the system, so removing them could crash your device.
Matt
Someone correct me if I'm wrong, please.
I believe that if you were to make your own ROM you could edit the registry and move the files before flashing it into your Uni.
At the same time you could rip out WMP and PIE, replacing them with more useful apps like TCPMP and Opera, putting these programs into the 128MB flash instead of the 64MB storage. However, after reading a thread here about using MP3 ringtones and having WMP doing the decoding, I wonder how integrated it is and just what would happen if you took it (and it's registry entries) out of your system. Maybe just taking some crap like the Welcome program and some help/graphics files would leave you enough room in ROM to do this?
Grr, I should really get on and try this so that I can speak with certainty, shouldn't I?
-------> Is POSSIBLE to put ADOBE and POWERPOINT in MEMORY CARD to increase space??
Is possible to cut Power Point (2,29 mb) and AdobePDFreader(1,91mb) from the main memory and put them into the memory card??
It would increse a lot main memory space...
Experts, let me know if it's possible....
And what about all the files called "HH_WEATHER...", I have an other program fot meteo forecasts, so I don't use the original one... Is it possible remove all these files?? (I think that they are all images, I only opened a few, and they were all forecast images...)
BYE BYE......
the things you mentioned is probably burned into rom - you won't be able to remove it.
ww2250 said:
the things you mentioned is probably burned into rom - you won't be able to remove it.
Click to expand...
Click to collapse
Yes, I know..
But I lose the warranty if I install a cooked rom....
If my device in future won't work correctly (or don't work at all) I wouldn't be able to put the original rom back??
Alternative Solution
You could compress the two executables with UPX and use Resco Explorer to overwrite them in the ROM. That won't save you as much space as moving them to external memory, but by compressing the files, you will save a decent amount of space.
tyr0ne said:
You could compress the two executables with UPX and use Resco Explorer to overwrite them in the ROM. That won't save you as much space as moving them to external memory, but by compressing the files, you will save a decent amount of space.
Click to expand...
Click to collapse
Actually that will use MORE space. If the files are in ROM they arent using any of you Program RAM. If you overwrite the ROM files like this the new files will be in RAM!!!
flykthewiz said:
Actually that will use MORE space. If the files are in ROM they arent using any of you Program RAM. If you overwrite the ROM files like this the new files will be in RAM!!!
Click to expand...
Click to collapse
Are you sure about that??
Do you mean that, if I compress these files, when I replaced the originale ones with the newest, the pocket pc places them into the ram and not the rom??
How is possible it??
So I can do this operation or not?
I would be happy if only I had 2/3 mb more....
flykthewiz said:
Actually that will use MORE space. If the files are in ROM they arent using any of you Program RAM. If you overwrite the ROM files like this the new files will be in RAM!!!
Click to expand...
Click to collapse
Anyone know this inconveniet??
the only thing is with anything that you add to your ppc after initialization... it stores it to the ram, not the rom, you would have to actually cook a similar rom to your original rom to have the new stuff in there, and all you would have to do is get the official ruu for your device before you call back in, and you are good to go, thats what i do!
MrGalione973 said:
the only thing is with anything that you add to your ppc after initialization... it stores it to the ram, not the rom, you would have to actually cook a similar rom to your original rom to have the new stuff in there, and all you would have to do is get the official ruu for your device before you call back in, and you are good to go, thats what i do!
Click to expand...
Click to collapse
Ok, perfect...
I think that in the future I'll try a cooked rom, I know that it increase the space, a lot!
The only thing that worried me is the following:
If I have to repair the device, I must put the original rom back, but if I can't do it (ex my device doesn't start correctly)?
I had a Nokia N73 brand with my operator Tim, I have unbrand it (knowing to lose the warranty), but some months ago I must bring it to a Nokia Center, to repair.
And they don't see nothing about the difference between the original Imei and the actual one (that are different because you must do that to update yur firmware)....
flykthewiz said:
Actually that will use MORE space. If the files are in ROM they arent using any of you Program RAM. If you overwrite the ROM files like this the new files will be in RAM!!!
Click to expand...
Click to collapse
So u mean it's possible to replace a ROM file in the windows dir with another?
If so, HOW... i want to replace smartdialing.dll in my htc elf with another one that's patched containing another language(greek) but it doesn't seem to work.
Any help on this one?
larryg4 said:
So u mean it's possible to replace a ROM file in the windows dir with another?
If so, HOW... i want to replace smartdialing.dll in my htc elf with another one that's patched containing another language(greek) but it doesn't seem to work.
Any help on this one?
Click to expand...
Click to collapse
He talks about replace the file with resco explorer....
I think that you only have to copy the new file and paste it into the windows directory with resco....
Isnt it possible just to copy the program files to memory card and change the registry settings for those apps to point to new location?
jem777 said:
Isnt it possible just to copy the program files to memory card and change the registry settings for those apps to point to new location?
Click to expand...
Click to collapse
I would want know exactly this thing....
Anyone know??
jem777 said:
Isnt it possible just to copy the program files to memory card and change the registry settings for those apps to point to new location?
Click to expand...
Click to collapse
Some programs are hardcoded with paths in "\windows" directory - by moving stuffs around, things may break. Many programs that are expected to be in ROM fall in this class.
But then even if you are successful in "copying" it elsewhere, you won't be able to delete what's already in ROM. Overwriting it is just an masking action. ROM is ROM - follow me, Read Only Memory. Thus no memory is saved whatsoever.
Unless you flash it somehow.
ww2250 said:
Some programs are hardcoded with paths in "\windows" directory - by moving stuffs around, things may break. Many programs that are expected to be in ROM fall in this class.
But then even if you are successful in "copying" it elsewhere, you won't be able to delete what's already in ROM. Overwriting it is just an masking action. ROM is ROM - follow me, Read Only Memory. Thus no memory is saved whatsoever.
Unless you flash it somehow.
Click to expand...
Click to collapse
Ok, I understand the problem..
Tell me only the last thing....
If I copy the files to the memory card and then I create some shortcuts to these files, and replace them into the windows folder, do you think that they'll work or not??
When the pocket pc try to use them, It'll find the shortcut(and not the program itself) but this will direct the pocket pc to the program itself....
Would it work??
If I copy the files to the memory card and then I create some shortcuts to these files, and replace them into the windows folder, do you think that they'll work or not??
flaviopac said:
If I copy the files to the memory card and then I create some shortcuts to these files, and replace them into the windows folder, do you think that they'll work or not??
Click to expand...
Click to collapse
Noone know if it would run??
re-read my earller post. the answer is there already. if you find it difficult to understand, why don't you try it out yourself? it's incredibly simple.
Today I just tried this, I compressed my softwares which I have cooked in my ROM using UPX4PPC and cooked them in the ROM. As I have a small 32MB ROM (Himalaya), if this is possible to do with the default OS dll & exe files, it would be very useful. As I noticed, there is no big difference in the loading time of compressed files & the original. I searched the forum, but found nothing on compression of system OS files. Is there anyone who have done this before? Is this ok to do with .net CF dll & other large dll & exe files in ROM...?
shiranmotha said:
Today I just tried this, I compressed my softwares which I have cooked in my ROM using UPX4PPC and cooked them in the ROM. As I have a small 32MB ROM (Himalaya), if this is possible to do with the default OS dll & exe files, it would be very useful. As I noticed, there is no big difference in the loading time of compressed files & the original. I searched the forum, but found nothing on compression of system OS files. Is there anyone who have done this before? Is this ok to do with .net CF dll & other large dll & exe files in ROM...?
Click to expand...
Click to collapse
so you're compressing before cooking? interesting. all's working ok?
fredcatsmommy said:
so you're compressing before cooking? interesting. all's working ok?
Click to expand...
Click to collapse
EXE files can be compressed successfully. But when I compress all the dll files, ROM is not starting. Compression of some dll files works fine. So I wanna find which files can be compressed and which are not.
shiranmotha said:
EXE files can be compressed successfully. But when I compress all the dll files, ROM is not starting. Compression of some dll files works fine. So I wanna find which files can be compressed and which are not.
Click to expand...
Click to collapse
Does it go for SYS and OEM?
Interesting finding!!!
I'll be tunned
Regards,
Jaime.
Tapped "Save Changes" twice.
http://forum.xda-developers.com/showthread.php?t=397792
http://forum.xda-developers.com/showthread.php?t=265175
http://forum.xda-developers.com/showthread.php?t=335982
http://forum.xda-developers.com/archive/index.php/t-276884.html
..and so on..
maybe it's time to READ, not write?
few words about fighting for every goddamn kilobyte..
some exes or dlls cannot be upx-ed, NOTHING from rom/xip cannot be upx-ed,
do not try to upx .netcf soft, or its oempackage dlls, some dlls from mms oempack may lose its functions; isilo and some offROM soft will break, DO NOT upx today plugins(2 be sure), TCPMP plugins CAN be upxed, CPL-s usually CAN be upxed,
some upxed dlls may have ADVERSE effect on memory( i mean clean boot mem and so on), especially dll's that are launched after boot(..erm, resident, crucial ones).
whole art is to get thin line between making XIPmodules and upxed files....RAM-ROM loss, i mean.
and stability.
if you need more romspace, you will need do more, than simple upxpackclick, trust me...
look at size of tahoma and courier .ttf from DIFFERENT kitchens(old/new).
gain.
look at things that you will not use - cut it.
gain.
do not use stupid, trendy soft, until you MUST.
gain.
erase stupid html help files, not crucial temptates, etc
gain.
edit welcomehead.96.png(it may have 160 kb, or 2 kb...)
delete services and things that you do not need: i.e.sqm service(well..not delete = dummy), maybe wlive etc...delete mms oempack, if you do not need it - you CAN install it later..remove ppt.exe, its dlls and mui etc..
gain.
you need 2 mb skin instead of thinking/editing?
loss.
you want to have 1936237569423 home clones at once?
loss.
you do upx 23194673459826032194 - dlls exes AT once and flash...
loss(of time).
no hklm/init editing?
loss.
no reshacking(i.e. dialer skins, some keyboards, soft gfx etc)?
loss.
no unused dll's deleting?
loss.
you are not able to reedit soft gfx to optimize its size...
LOSS.
etc etc..
for going to extreme it is possible to cut XIP(but leaving crucial sys contents instead), but it is rather...risky.
i do not know more bout it..
i loaded >26-28 mb of useful soft/dlls/cpls/plugins/fonts into my rom, btw(wizard). 6.1.
84 apps, or so..
but ignore me...just short outburst..it is so hard to find something interesting there lately...
btw, usually it is safe to upx camera.exe.
worth it, imo.
safe files to be upxed, imo:
ppt.exe
word.exe
pxl.exe
and many more, of course.
there is no big difference in the loading time of compressed files & the original.
Click to expand...
Click to collapse
romfiles, maybe, but 9 mb file vs 2 mb file from sd card...you know..
OT:
btw, remember: RGU files MUST be saved as UNICODE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
(that is very easy method to see first/second splash ONLY, nothin more..)
easy 2 forget.
well i use UPX for about 2 years in roms but I never sompress anything major in SYS folder except the Office pack, never upx .net (or it wil not work) some programs like solitaire and bubble breaker and calculator (spb one) can be compressed
2 years in roms but I never sompress anything major in SYS folder except the Office pack
Click to expand...
Click to collapse
well, you prolly did not need more space...for these 2 yrs.
EOT,sry.
good luck.
Bear in mind that rom's which have been upx'd take up MORE memory to run than non upx'd ones because some of the memory is not released. This has been hashed back and forth in detail in the previous threads but compressing everything in site is NOT the answer.
that rom's which have been upx'd take up MORE memory to run than non upx'd ones because some of the memory is not released.
Click to expand...
Click to collapse
agree...
idd, some - it may be not a problem, if it is not thing, that works ALL the time(crucial system dll, etc).
if it is..its useless to even try. loss may be quite..big, sometimes...
I am trying to save storage memory on my diamond. I want to delete the /Windows/ files Album Sample 01.jpg thru Album Sample 13.jpg which will free up several meg.
tried unsuccessfully with Total Commander...
any one help?
thanks
This means that they're in ROM and cannot be deleted
What you could do is make a image thats very small in data and rename to file names and overwrite with Total Commander.
You can do the same with music thats in ROM too zero length .mp3's
Hope that helps.
stylez said:
What you could do is make a image thats very small in data and rename to file names and overwrite with Total Commander.
You can do the same with music thats in ROM too zero length .mp3's
Hope that helps.
Click to expand...
Click to collapse
thats smart solution
dody said:
thats smart solution
Click to expand...
Click to collapse
smart but useless, since in this way you don't save anything: overwriting ROM files with smaller ones doesn't reduce disk usage but, vice-versa, increases it (since you'll still have the ROM files AND the new ones) also if only of some bytes
bbonzz said:
smart but useless, since in this way you don't save anything: overwriting ROM files with smaller ones doesn't reduce disk usage but, vice-versa, increases it (since you'll still have the ROM files AND the new ones) also if only of some bytes
Click to expand...
Click to collapse
Ah i get you as the files have to still be there for the ROM to be able to rewite the file, know what mean
Good idea though
I don't get you, stylez. "Overwriting" ROM files is only a verbal expression, since you don't really overwrite anything. When you copy to \windows a file that has the same name of a ROM file, simply the system reads the one on disk instead of the ROM one, that (simply for being in ROM) is still there and cannot be changed/edited/deleted.
So, if you "overwrite", for example, the abc.bmp ROM file with a 0 byte abc.bmp, the original one is still in ROM but the system don't read it anymore: instad it reads the 0 byte abc.bmp. And being a 0 byte file, you don't waste disk space, but as the same time you don't gain new space: you can try and see the free space before and after an overwrite with a 0 byte file
bbonzz said:
I don't get you, stylez. "Overwriting" ROM files is only a verbal expression, since you don't really overwrite anything. When you copy to \windows a file that has the same name of a ROM file, simply the system reads the one on disk instead of the ROM one, that (simply for being in ROM) is still there and cannot be changed/edited/deleted.
So, if you "overwrite", for example, the abc.bmp ROM file with a 0 byte abc.bmp, the original one is still in ROM but the system don't read it anymore: instad it reads the 0 byte abc.bmp. And being a 0 byte file, you don't waste disk space, but as the same time you don't gain new space: you can try and see the free space before and after an overwrite with a 0 byte file
Click to expand...
Click to collapse
You misread me as i agreed with you "not in the right terminology"
Thanks for expanation
Sorry for a quick idea that doesn't work and if had of thought about it logically would have known "spending too many hours editing .dll & .cprs"
stylez said:
i agreed with you "not in the right terminology"
Click to expand...
Click to collapse
lol