Database Users

PPC 2003 and mkrom

Any brave soul try using mkrom in conjucntion with the 2003 ROM? I think I might give it a shot here in a bit but wanted to know if anybody had tried it yet...

I've managed to build a 2003 ROM. It's extremely tricky though. I'm working on customizing a ROM similar to the XDA Developers SER - as soon as I get some free time
I'd like to acknowledge all the help given to me by Developer Itsme in this endeavor.
Let me know any suggestions you may have for the new ROM.

sheran_g,
i didn't know u could use mkrom with 2003 rom image. can u please post how u did it? i created a special version based on SE 1.1 rom but would like to put the same programs into the new rom. any help is appreciated.
thanks
alex

sheran_g said:
I've managed to build a 2003 ROM. It's extremely tricky though. I'm working on customizing a ROM similar to the XDA Developers SER - as soon as I get some free time
I'd like to acknowledge all the help given to me by Developer Itsme in this endeavor.
Let me know any suggestions you may have for the new ROM.
Click to expand...
Click to collapse
What's tricky about it...?

The modified registry file you make does not get picked up at the device startup. You need to manually inject the memory address of the modified registry file into the ROM in order for it to get picked up.

my latest romtools can be found at romtools
now it calls dumprom to find and fix the filedata offsets.
I think they should now build 2003 roms.

sheran_g,
can u post the steps that u take to buid it? i'm trying right now and its not working. i'm having little problems. can u post ur default.reg and initobj.txt? any other help is apreciated.
thanks
alex

Ok. Here they are in a nutshell:
Get the latest romtools.
Make the following dirs: romfiles, cfg, tmp, out, files, files1, files2
Split the ROM into Bootloader, bootimage, OS image, xipchain into the 'cfg' dir.
Dump the files in the OS image into a 'romfiles' dir.
Get the default registry file, initobj & initdb files into your 'cfg' dir.
Make changes to your default.reg and initobj.txt
Place any files you want loaded in the ROM into the 'files' dir.
Run 'mkrom.sh'
You should then have your new ROM. I'm sorry if it's extremely brief; you'll have to make do with this and the README file in the romtools archive file for now. You'll find my default.reg and initobj.txt files on my site: www.zensay.com/qtek/mkrom

sheran_g,
Have you created a decent working custom WM2003 ROM?
If so what Apps have you added?
How much ROM space does it use?

I've not added any apps to my ROM. I have only added a carrier logo file and made some changes to the registry. So I cannot comment on ROM space yet. The ROM works fine.

sheran_g,
what command did u use to extract rom files? did u do it under windows or unix?
I'm having problems trying to dump the rom image. I don't know if its too much to ask, but can u zip ur directory and post it somewhere so i can download it? or if u can post commands that u ran to dump the 2003 rom?
thanks
alex

Hi,
could you include "O2 home zune" to the 2003 image, like in the 2002 3.19 GER. Its for Germany interested only!
AR :?:

home zone depends on specific 3.19 rilgsm features. which are not in 4.*

okay, used dumprom -4 -d files -q nk.nbf and extracted all files. Got could not find pointer for ofs 00000000 ERROR but all the files seem to be there. Trying to figure this out. Saw the above abreviated directions but am fumbling around. Anyone have concise directions?
Val

Anyone? Just give me a good hint then please.

Hi all!
When i overwrite the rilgsm.dll file in the t-mobile 4.0.10 image with the rilgsm.dll from the O2 GER 3.19 image, i could use the "O2 home zone" option with the hz.exe in Starup directory? rilgsm.dll from german image hes 'at+creg=2' string in it. probably the RIL_GetCellTowerInfo call is now implemented. When it can work, how could i write the german rilgsm.dll to the image? I haven't linux, could somebody cook the image for me?
here is the germen rilgsm.dll and the hz.exe for the "home zone" funktion! http://www.nokiaprog.de/XDA/home_zone.zip
THX
PS: Sorry, my english! ;-)
AR

the homezone enabled rilgsm.dll depends on other dll's and exe's.
probably ril.dll, stk.exe, cell*.dll and maybe more, I have not tried
replacing all.
you don't need to build a new rom in order to experiment with this, you
can just copy the desired files to \windows, to override the rom versions.

And I don't think it works with the RIL_GetCellTowerInfo call,
but adds some notification events.
to change the CREG setting you need to call RIL_DevSpecific with parameter 25 ( to turn it on ) or 26 ( to turn it off )
even though that does not seem to be how hz.exe does it.

Hi,
I opened the image file in the Hex editor and renamed the file there rilgsm.dll. Then I flashed the image, which was phone probably deactivated, because rilgsm.dll was missing. Then I copied over ActiveSync the German rilgsm.dll into the Windows directory, XDA reset and he not accept the file. I assume because the file was not in the EPROM memory! Therefore I wanted to have rilgsm.dll first times in the image!
AR

XDA developer Itsme said:
my latest romtools can be found at romtools
now it calls dumprom to find and fix the filedata offsets.
I think they should now build 2003 roms.
Click to expand...
Click to collapse
Is there any other way i can access this site or I can download this files, the sites are block here in my country, Please Help
Ronnie

mkrom (Extract of Rom Kitchen) Add files question

Hi All
I hope someone can help with the following problem.
I had wanted to use Mkrom on 2003 roms but after encountering problems with rom addresses and on KP2L's advice I switched to the "Rom Kitchen" as the code has been updated to handle 2002 and 2003.
I did not want to run the whole thing as I don't know much about Web servers on Unix so I just downloaded the 2003 directory and added back the missing folders and tools. After converting the files I am able to run ./mkrom.sh and make a "raw" .nb1 image that loads O.K to my XDA
The problem starts when I try to add files.
Trying a simple example of just placing ssnap.exe in the files folder and not bothering with links/ subfolders etc ./mkrom seems to work in as much that it picks up the files>transfers them to files 1/ 2 adds the files from cfg and > to the XDA1/2 .bin together with xip and loads to the rom under XDA_Developers 1/2. When this Rom is installed the XDA freezes at the bootsplash screen (Not completely, if you press the volume button it comes up to the start screen but the screen is miles out of calibration and most of the menus are missing) To test this further I downloaded a rom from Jeffs kitchen and stripped the files for the cfg/files folder and re-ran ./mkrom.sh but I get the same problem .
I have run lots of UltraEdit "Compare" reports,of all of the cfg/dumprom output files, between mine and Jeffs, and apart from some addressing differences all the data is getting to the rom. (I can post the reports if anyone wants them)
I suspect, although I'm useualy wrong, it's data "type"/ conversion conflict and wonder if under a full Rom Kitchen the files are converted in some way before being placed in the files folder prior to ./mkrom processing ?
As a last resort, I guess, I will have to set up the Web server (I have got one just never used it) and do the whole thing but hope to avoid it with a bit of help.
PLEASE :?: :?: :?:
Thanks
Richard

O.K I guess the question was too long/boring lets try this:
Do the scripts in Rom Kitchen make any changes to the files to be added to rom prior to processing by ./mkrom.sh
Richard

Richjn said:
Do the scripts in Rom Kitchen make any changes to the files to be added to rom prior to processing by ./mkrom.sh
Click to expand...
Click to collapse
No: the script basically just sticks the files into /files and then runs mkrom.sh
Not sure why your scenario isn't working, it sounds like it should...

Remove files from ROM

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

Is there a way to override a rom file?

Is there a way to override a rom file?
I found welcomehead.192.png the windows boot screen, not the initial imate one, the blue windows one, ive edited the png, but cant replace the file as it is in rom, any suggestions as how to do this? or is it wait until someone works out how to open the nbf file and then change that way?
Theres nothing in the registry that i can find that points to this file

anyone?

just overwrite the file with the same name. ignore errors

1. As sama says, just use a proper file explorer (Resco/Total) to overwrite the ROM file. If you delete the new file the old one will still be there in ROM.
2. The ROMs can be decoded, you can change the ROM then flash it. This is not a safe thing to do, and is complicated. However, this is a total waste of time (hours) for a 100KB image file unless you really can't afford 100KB in your Programs Memory.
3. If you want, you can also change the "initial imate one" too. Buzz has the tools and instructions on his site (http://buzzdev.net). This will be a flash job, but takes up no space and a hard reset won't wipe it.
Hope this helps.

Find ROM version from OS.nb file

Hi,
i know it's possible to know some values starting from the .nbf header (like device, lang, version, etc) but what i'd really like to know is the ROM version just from the OS image extracted from the nk.nbf file with Typho5.exe (typhoonnbfdecod.pl)
let's say i have such a file "80040000-OS_0.nb" and i forgot from which installer i extracted it from and would like to discover it then. Any clues?
tx
UPDATE:
should i have waited a couple of days and answer would fall on my lap
http://forum.xda-developers.com/showthread.php?t=296861
http://forum.xda-developers.com/showthread.php?t=263201&highlight=find+ROM*+version