Database Users

no operator rom found

hello,
I just tried to compile a new rom image using the mkrom tool and when my device boots up with the new rom the autoconfigure list is empty.
While i was compiling i noticed that i got an error message saying: "no operator rom found". i have all the files from mkrom extracted and cfg directory contains operator.cfg. operator directory contains .reg files. Any ideas why its not building the operator rom?
thanks
alex

Did you change anything in the operator directory? It's touchy about the format of these binary files. Can you post the exact 'mkrom' output?

thanks for reply. i initially tried to change the operator files to put GPRS settings for T-mobile USA. after that i replaced the files from mkrom archive and tried to compile again and got the same error. here is mkrom output.
alex
rommap: 80000000-81f00000
80000000 - 80040000 -- bootloaer 0 files 1 modules
80040000 - 8026a804 -- kernel 13 files 11 modules
802c2000 - 8057d330 9 OS 15 files 32 modules
80580000 - 8075a69c 8 SHELL 79 files 27 modules
80780000 - 80a13b04 7 BROWSING 9 files 14 modules
80a40000 - 80d8a33c 6 COREAPPS 46 files 30 modules
80dc0000 - 80ebd150 5 SYNC 12 files 22 modules
80ec0000 - 810388e0 4 24MAPPS 13 files 13 modules
81080000 - 81348248 3 24MCONSUMER 69 files 1 modules
81400000 - 814019a4 -- xip chain 10 xip entries
81440000 - 817f6f14 1 MISC 209 files 40 modules
81800000 - 818f1888 10 XDADEVELOPERS_1 16 files 0 modules
81900000 - 81925800 -- bitmap : f9fff9ff .. f9fff9ff
81940000 - 81ba28c8 11 XDADEVELOPERS_2 109 files 0 modules
81bc0000 - 81bffb16 -- operator rom 11 files
write xip block starting at 81800000, with 14 files
write xip block starting at 81940000, with 152 files
stripping BMP header
316+0 records in
316+0 records out
013c0000 added mainrom
1+0 records in
1+0 records out
013d0000 added xipchain
60+0 records in
60+0 records out
017c0000 added MISC
10+1 records in
11+0 records out
01870000 added xda1
153600+0 records in
2+1 records out
018e5800 added bitmap
14+1 records in
15+0 records out
01cc0000 added xda2
0+1 records in
1+0 records out
01d00000 added operator rom
0+0 records in
0+0 records out
01ec0000 added end
rommap: 80000000-80040000, 80040000-81f00000
no operator rom found
80000000 - 80040000 -- bootloaer 0 files 1 modules
80040000 - 8026a804 -- kernel 13 files 11 modules
802c2000 - 8057d330 9 OS 15 files 32 modules
80580000 - 8075a69c 8 SHELL 79 files 27 modules
80780000 - 80a13b04 7 BROWSING 9 files 14 modules
80a40000 - 80d8a33c 6 COREAPPS 46 files 30 modules
80dc0000 - 80ebd150 5 SYNC 12 files 22 modules
80ec0000 - 810388e0 4 24MAPPS 13 files 13 modules
81080000 - 81348248 3 24MCONSUMER 69 files 1 modules
81400000 - 814019a4 -- xip chain 10 xip entries
81440000 - 817f6f14 1 MISC 209 files 40 modules
81800000 - 818a7a50 10 XDADEVELOPERS_1 14 files 0 modules
81900000 - 81925800 -- bitmap : ffffffff .. ffffffff
81940000 - 81cca488 11 XDADEVELOPERS_2 152 files 0 modules

mkrom with 2003 "mkrom.sh" code

Hi All
I am trying to setup mkrom to handle PPC2003. I have extracted / converted all of the files from a "bare" 4.00.05 rom from Jef's Kitchen and amended the operator files etc and am able to generate new roms. I now need to change the code in the mkrom.sh file to change the xda1.bin and xda2.bin, and so on, addresses to match the 2003 rom layout. I have the relevant details but my question is can I simply substitute the new adresses into the .sh file or is there more to it ?
Thanks for any help
Richard

the latest version of mkrom has all its rom dependent parameters in 'cfg/params' and instead of all the 'dd' stuff, I now changed splitrom to handle all the manipulating of image files.
the offsets you see in mkrom are defaults for 3.17.
the latest mkrom you can find in http://xda-developers.com/DemoKitchen/data/00_Base ROM/4.00.05 ENG ppc2003/_/mkrom.sh

Itsme
Thanks again
Great site, Great team
Richard

Itsme
I have downloaded the 4.00.05 directory of Rom Kitchen and placed the required files in the correct folders and ran mkrom. On the first attempt the program reported "can't find dumprom" so I copied in the entire toolset and ran mkrom again this time I'm getting an overlap error as below:
write xip block starting at 81740000, with 2 files
write xip block starting at 81b00000, with 0 files
!!! your rom is not known to me: md5: dad2e3cad6095282bf1d58ccf12171e8
this bootloader seems to be V5.22 2003-05-15 17:46:55
no operator rom found
80000000 - 80040000 -- bootloader 0 files 1 modules
80040000 - 8015df78 9 XIPKERNEL 5 files 5 modules
80180000 - 80376f10 8 KERNEL 10 files 14 modules
80380000 - 8064306c 7 OS 20 files 36 modules
80670000 - 80be66a8 6 SHELL 107 files 88 modules
80c00000 - 8102ce98 5 BROWSING 11 files 36 modules
81050000 - 813ef114 4 COREAPPS 95 files 44 modules
81400000 - 815d2238 3 EXAPPS 34 files 7 modules
815f0000 - 8171bc7c 2 PHONE 56 files 19 modules
81740000 - 81766e90 10 XDA_DEVELOPERS1 2 files 0 modules
81780000 - 81781c34 -- xip chain 11 xip entries
817c0000 - 81ca1b44 1 MISC 225 files 42 modules
81b00000 - 81b01054 11 XDA_DEVELOPERS2 0 files 0 modules
81ec0000 - 81ee5800 -- bitmap : f9fff9ff .. f9fff9ff
Error creating new rom
Overlap detected
1 MISC 225 files 42 modules
11 XDA_DEVELOPERS2 0 files 0 modules
This output comes from a run with a Tmobile "bare" rom but I get the same with a 4.00.05 rom from Jeffs kitchen.
I had not wanted to install the whole kitchen if I could help it and from the code it doesn't look as if I would need to but something is wrong somewhere. I would be verry grateful if you could offer any thoughts.
Thanks
Richard

All sorted now
Richard

The kitchen is back up !!!

My friend's box is back up !
There was a problem which caused workspace directories not to be deleted under some circumstances, which caused the 'all workspaces are busy' problem. If all is well this problem is now also fixed.
--
Jeff

First of all without yor kitchen we will not eat, thank you.
I suggest if you can put a version or last update date so the visitor check if there is a changes and highlite the new lines.
Thanks.

Sigh,
And back down again...
Guess we'll have to wait for it to come back up.

http://cuba.calyx.nl/~jsummers/ROMkitchen/
Hi! Jeff
Thks for your time, effort you spent to create the web page.
I'm being using 3.17 cook rom it for a few weeks. and is wonderful.
Any chances that U fit in the 3.20 rom to your page?
thks in advance. :wink:

FYI:
Jeff's kitchen seems fine now...

Jeff, your kitchen is fantastic!! Thanks for all the great work!

@ Jeff. Thanks for the great work. Decided to try out the new anti-theft feature and received this when cooking:
echo Warning: OS type not detected, you may need to set tounicode variable manuallywrite xip block starting at 81740000, with 3 fileswrite xip block starting at 81b00000, with 144 files!!! your rom is not known to me: md5: 1cd007bbffa268b12b7968cabb7cc75fthis bootloader seems to be V5.22 2003-05-15 17:46:55no operator rom found80000000 - 80040000 -- bootloader 0 files 1 modules80040000 - 8015d5cc 9 XIPKERNEL 5 files 5 modules80180000 - 80375bdc 8 KERNEL 10 files 14 modules80380000 - 8064306c 7 OS 20 files 36 modules80670000 - 80be66a8 6 SHELL 107 files 88 modules80c00000 - 8102ce98 5 BROWSING 11 files 36 modules81050000 - 813ef114 4 COREAPPS 95 files 44 modules81400000 - 815d2238 3 EXAPPS 34 files 7 modules815f0000 - 8171bc7c 2 PHONE 56 files 19 modules81740000 - 8177ffec 10 XDA_DEVELOPERS1 3 files 0 modules81780000 - 81781c34 -- xip chain 11 xip entries817c0000 - 81ae4338 1 MISC 109 files 42 modules81b00000 - 81eadc2c 11 XDA_DEVELOPERS2 144 files 0 modules81ec0000 - 81ee5800 -- bitmap : f9fff9ff .. f9fff9ff adding: NK.nb1zip I/O error: No space left on devicezip error: Output file write failure (write error on zip file)

ROM Tmobile 4.00.21

I am working on putting the tmobile 4.00.21 file in a kitchen. I have the .nbf and the .nb1 file. How do I go about getting the other files that are needed? I tried running one of the commands I found here in the forum but it tells me to extract the parts manually.
[[email protected] _]# perl setup.sh nk.nbf
!!! your rom is not known to me: md5: 35213a7a7f80ed9a6284aa5e41f08ff1
this bootloader seems to be V5.22 2003-05-15 17:46:55
no operator rom found
80000000 - 80040000 -- bootloader 0 files 1 modules
80040000 - 8015df08 9 XIPKERNEL 5 files 5 modules
80180000 - 80376ef0 8 KERNEL 10 files 14 modules
80380000 - 8064306c 7 OS 20 files 36 modules
80670000 - 80be66a8 6 SHELL 107 files 88 modules
80c00000 - 8102ce98 5 BROWSING 11 files 36 modules
81050000 - 813ef114 4 COREAPPS 95 files 44 modules
81400000 - 815d2238 3 EXAPPS 34 files 7 modules
815f0000 - 8171bc7c 2 PHONE 56 files 19 modules
81780000 - 81781714 -- xip chain 9 xip entries
817c0000 - 81bf60f8 1 MISC 212 files 42 modules
81900000 - 81925800 -- bitmap : 30000be5 .. 010000ea
OVERLAP DETECTED:
1 MISC 212 files 42 modules
-- bitmap : 30000be5 .. 010000ea
please extract parts manually
[[email protected] _]#

params
make sure you're setting the right params in cfg:
wincever=4
start1=81740000
size1=00040000
start2=81c00000
size2=00300000
startbmp=81ec0000
startop=81c00000
than you can dumprom ... delete all files in the files directory and place whatever files you want into there (try to stay in 81ec0000 = ~3Mb)
Decebal

So you are saying that in order to get the files necessary to put in Kitchen that I need to get a params file from one of the others and change the values to what you have listed. Then when I run dumprom it will extract the bootimage, xipchain, and bootloader files?

How large is default.fdf extracted by dumprom from 4.xx roms

I am doing mkrom for 4.xx roms XDAI. the default.fdf extracted from the rom 4.00.11 and other 4.00.xx roms are only about 12k in size. which is aparantly incorrect. The default.fdf extracted from 3.17 rom is about 333k.
Anyone can help out? I did use the -4 option with dumprom.

that is correct, in 4.x more settings have moved to the .rgu files.
the .rgu files are unicode ascii files. in a format similar to what normal regedit uses.

thanks for pointing that out. However, still get into trouble.
downloaded the romtool, use 4.00.11 rom image. follow the instruction. I can cook up a rom without putting any files in the "files" directory.
however, when I put in about 3M files in "files" directory. all the rest not modified, XDA won't boot up with the cooked rom. froze at the screen shows the image and the rom version and radio stack version number.
I got from the kitchen that I can put 3906k files inside this rom. is that right?

the exact size of files is a bit hard to calculate, easiest is to check the result for overlapping blocks. splitrom will usually tell you this.
btw, try to post a question only once, it doesn't help the discussion if I the same question is in multiple threads at the same time.

first apology for posting twice. first did at the end of one tread and thought it might deserve its own thread. and kept following up in both.
still struggled.
here is the output of splitrom.
A), the rom that added files
!!! your rom is not known to me: md5: 3435ca5403918430758c5d407a6f53af
this bootloader seems to be V5.22 2003-05-15 17:46:55
no operator rom found
no bitmap found
80000000 - 80040000 -- bootloader 0 files 1 modules
80040000 - 8015d5cc 9 XIPKERNEL 5 files 5 modules
80180000 - 80375bdc 8 KERNEL 10 files 14 modules
80380000 - 8064306c 7 OS 20 files 36 modules
80670000 - 80be66a8 6 SHELL 107 files 88 modules
80c00000 - 8102ce98 5 BROWSING 11 files 36 modules
81050000 - 813ef114 4 COREAPPS 95 files 44 modules
81400000 - 815d2238 3 EXAPPS 34 files 7 modules
815f0000 - 8171bc7c 2 PHONE 56 files 19 modules
81740000 - 8177ff00 12 XDA_DEVELOPERS1 5 files 0 modules
81780000 - 81782154 -- xip chain 13 xip entries
817c0000 - 81ae4338 1 MISC 109 files 42 modules
81b00000 - 81e7eea0 13 XDA_DEVELOPERS2 7 files 0 modules
B). the rom without files added
!!! your rom is not known to me: md5: a0ea95afdd6f7878bff3f41bce0fa291
this bootloader seems to be V5.22 2003-05-15 17:46:55
no operator rom found
no bitmap found
80000000 - 80040000 -- bootloader 0 files 1 modules
80040000 - 8015d5cc 9 XIPKERNEL 5 files 5 modules
80180000 - 80375bdc 8 KERNEL 10 files 14 modules
80380000 - 8064306c 7 OS 20 files 36 modules
80670000 - 80be66a8 6 SHELL 107 files 88 modules
80c00000 - 8102ce98 5 BROWSING 11 files 36 modules
81050000 - 813ef114 4 COREAPPS 95 files 44 modules
81400000 - 815d2238 3 EXAPPS 34 files 7 modules
815f0000 - 8171bc7c 2 PHONE 56 files 19 modules
81740000 - 817637b0 10 XDA_DEVELOPERS1 3 files 0 modules
81780000 - 81781c34 -- xip chain 11 xip entries
817c0000 - 81ae4338 1 MISC 109 files 42 modules
81b00000 - 81b01054 11 XDA_DEVELOPERS2 0 files 0 modules
I don't see any overlap in either of them, as far as the address are concerned. the second rom works and the first one does not