Database Users

mkrom hangs on welcome screen

I just make the special edition ROM trhought mkrom and I obtain the.nb1 file, but when I flash my xd and make the cold reset, it hangs on the welcome screen, it print the 3 lines in red in the right bottom and after that ..... Nothing....... sniff
Anyone could help me????
I used the .nbf file that comes with the program A of O2.
Thks

that means that the windows kernel, and gsm have initialized.
the system should then proceed to execute the stuff mentioned in registry key HKEY_LOCAL_MACHINE\init.
maybe something went wrong with default.fdf?

I use the default.fdf that comes with the mkrom.zip, I just extract it and copy the nk.nbf file and proceed, I didn´t modify anything.
thks

I try to make another ROM with diferent Default.fdf but it hangs too.
it could be the NK.nbf file???
can you tell me where is a link fot one NK.nbf valid?
I´m going crazy :shock: jeje
thanks

if you use a different source rom, you need to change your default.fdf to
the one from that rom.

thanks for your patience,
I extract the default.fdf from the NK.nbf with dumprom.exe.
and then I use the fdf2reg.pl to create the default.reg and I put this file in the cfg directory, and after that I execute mkrom (sh mkrom.sh NK.nbf)
is that correct???
thanks

I think that the nbf file that I´m using is not a correct verion.
I tried to make a nbf file form jeff´s page but it doesn´t work with the nbf selection.
Do you know where can I find a nbf file that works with mkrom???

use mkrom to cook 4.00.xx rom, a tutorial and bug report

Spent a lot of time on it, trying to figure out what went wrong with mkrom when cooking 4.00.xx roms. finally figured it, well, almostly. here is a short step by step tutorial for people who do not want to set up the complicated kitchen but wish to use mkrom as in the good old 3.17 time.
I assume you already know the rom flush process already, if given a NBF file. also you need a linux box with perl.
I know quite a few people struggled and have not had a clue. and I believe there is some bugs in the mkrom package that gives the trouble.
1. download the newest mkrom from http://xda-developers.com/~itsme/download/mkrom_136.zip. this is the only piece of software you would need.
2. unpack it to, say mkrom, directory. then make directories cfg
3. get hold of a copy of rom file and its corresponding paramter files. the parameter files can be obtained from the demo kitch download ftp://kitchen:[email protected]/data look inside the "00_base ROM" and the parameter files should be under cfg directory of each rom directory. bascially the parameter files tells mkrom, where to start to put added files and how large space there is. there are two blocks of space that can be used. so the file has format
wincever=4
start1=81740000
size1=00040000
start2=81b00000
size2=003c0000
startbmp=81ec0000
startop=81b00000
the first three lines are same for all 4.00.xx roms, start2 varies for different roms, startbmp is also the same for all roms. startop should be the same as start2. size2 will be startbmp-start2, remember they are all in hex. you can calculate how large space there is once you get hold of the start2 parameter.
anyway, put the parameter files under the mkrom/cfg directory, with name "params"
4. copy a rom file (.nbf), say rom.nbf, into mkrom directory and run "./setup rom.nbf". this will creates several files under cfg.
5. mkdir a directory mkrom/romfile, enter it and make another directory file , then type "../dumprom ../cfg/rom.nb1 -4 -d file"
here comes the first bug. the setup.sh tells you that dumprom can only be used in windows box. but in fact, there is a compiled dumprom for linux in the directory (you might need to set it to be executable though). however, this linux version does not put extracted files into the "file" directory as it is supposed to, instead it just write file as "file\xxx" where xxx is the actual file name extracted from rom. it is a bug but as long as we know it, not a big deal. the is someone posted a correct version of dumprom in this forum though.
6. you should be able to find three files (or with the "file\" prefix added) with name default.fdf initobj.dat initdb.ini. these are the three files that needs to be process as indicated by setup.sh. follow the instruction to create the default.reg initobj.txt initdb.ini and copy them to cfg directory.
7. make a directory mkdir/files. you are ready to create a clean rom now by running "./mkrom output.nbf", the created output.nbf should be fine.
So far so good, followed the instruction of mkrom. next would need to add our files. then comes the problem. if you add files into the mkrom/files directory, and run "./mkrom output.nbf" again, it is almost definitely that the created rom is bad. I am not 100% sure why, but here is what I believe:
the mkrom script scan files in the "files" directory and put files in there into the "files1", "files2" directory, each of them is supposed to fill the two space in rom starting from "start1" and "start2" in parameter file. the size of files under "file1" should be less than "size1", similar "files2" and 'size2". when mkrom does this, it is highly possible that the three critial files "default.fdf, initobj.dat, initdb.ini" are placed into "files2" directory instead of "files1" directory and renders the rom bad.
here is what I did
edit the mkrom.sh, delete the line that splits files in "files" into "files1, files2" directory. change the three lines that convert the three critial files so that these three files are created in "files1" directory instead of "files" directory. then put your files into "files1" and "files2". just be careful, keep the size less than specified by "size1" and "size2".
then you can run "./mkrom.sh output.nbf" as before, and the resulted rom will be good.
hope this helps. however still a couple of problems
1. the fdf2reg.pl won't recoganize the default.fdf extracted from 4.00.21 rom or 4.01.00 rom
2. if i change the content of initobj.txt, the created rom won't boot. I might have done something wrong in initobj.txt though. but I used to be able to do this for 3.17 rom
3. I did not try to modify registry, as my only purpose is to put my files into ROM to save space. all registry can be done later by installing the software and choose not to overwrite existing files in ROM. must simpler.

the unix version of dumprom does not decompress files, that is why your default.fdf etc seem corrupted.
this is because I only have the decompression code in the form of a binary library, which I have not figured out how to link to under linux.
the only use of dumprom under unix is to find the offsets in rom where filepointers to default.fdf etc should be patched.
I should maybe disable the '-f' option in dumprom for the unix version, to make things less confusing.

but it looks to me that the dumprom under linux worked for pre- 4.00.16 rom. only not for after 4.00.21 roms. so are they different?

maybe the default.fdf was not compressed in the 3.x roms?
I am quite sure it does not work for compressed files under linux - I just did not implement the compression routines.

dumprom worked with 4.00.05 4.00.11 4.00.16 roms. I cooked 4.00.11 and 4.00.16 roms, and the rom was fine. I never used windows box during the process. only when i tried 4.00.21 and 4.01.00, there was error. anyway, i don't care, since I need as much rom as possible and 4.00.11 seems to be the best choice for me.
thanks for writting mkrom, a terrific tool. I don't like the way xda-developers.com promoting kitchen but not mkrom. mkrom is much simpler to setup and run, as long as you know about linux. the kitchen is much more complicated to get it to work and most people don't actually need such flexibility I believe.

ok i installed cygiwin and was with u till step 5, then i am lost.. when i run step 6 dumprom (in DOS) gives me an ewrror here atr the first few lines from dumprom( wiht latest ATT official release)
img 00000000 : hdr=8c0a1000 base=8c078000 commandlineoffset=8c077fe0
img 00040000 : hdr=800cdde0 base=80000000 commandlineoffset=7fffffe0
img 00180000 : hdr=8024db88 base=80000000 commandlineoffset=7fffffe0
img 00380000 : hdr=8039b334 base=80000000 commandlineoffset=7fffffe0
img 00670000 : hdr=80be2c40 base=80000000 commandlineoffset=7fffffe0
img 00c00000 : hdr=80e99400 base=80000000 commandlineoffset=7fffffe0
img 01050000 : hdr=813efc74 base=80000000 commandlineoffset=7fffffe0
img 01400000 : hdr=815d2ba4 base=80000000 commandlineoffset=7fffffe0
img 015f0000 : hdr=815f0650 base=80000000 commandlineoffset=7fffffe0
img 017c0000 : hdr=81bba0a4 base=80000000 commandlineoffset=7fffffe0
ERROR: could not find pointer for ofs 8c0a1000
invalid romhdr ofs 8c0a1000
ERROR: could not find pointer for ofs 00000000
7fffffe0 - 80000000 L00000020 unknown 30315750 452d3142 412d474e 2d30332e 2d353030 62373239 2d2d2d2d 2d2d2d2d
80000000 - 80000004 L00000004 romsection id=ea0003fe
80000004 - 80000040 L0000003c NUL
80000040 - 80000048 L00000008 'ECEC' -> 8c0a1000
errorsgalore...
so help me here how do i make sure the files extracted are all good also the size (as per ) windows explorer is 33+ not sure how all has been installed in the 32mb rom

did you get default.fdf initobj.dat initdb.ini out of dumprom. dumprom also reported tons of errors but as long as you get the three files out, it is ok.

Dumprom tries to figure out for each byte in the rom what it does. If it doesn't know it says 'unknown' this is not an error, just that dumprom could not determine the use of this byte. The 'could not find 00000000' message means that it encountered a NULL pointer somewhere in rom where it did not expect it, the other one is a pointer to RAM, which dumprom does not know exists. You can safely ignore these errors.
Dumprom was initially written to assist in figuring out what I did not know about the rom, so it tries to figure out stuff that is unknown. Later I added the code to extract files to it. Maybe I should split dumprom in one research tool, to do a detail examination of the rom, and one tool to only extract files.
Most files in rom are compressed, that is why they are more than 33M when uncompressed.

ok i understande the messages...
now here is what i did
ran ssnap and got a picture of the OS and did a compare and have a list of entries i want to add to registru and a folder with bunch of subfolders that need to be added on install
not sure how step 6 goes.. to convert the files to .reg and .txt and how/where do i add my files and registry entries....
any tips...

update...
i did fdf2reg and made a .reg file added my entries in there and then ran reg2fdf to recreatre the fdf...
i hope this is right now i need to fig out how to specify where the files i want added are to be copied i mean some go into windows some in new filders that need to be created...
plz tell me how to go forward.

you don't need to re-create the fdf file again, mkrom does it for you, you only need to take care of the default.reg file under cfg
I am not sure whether you can put files under directories other than \windows only. I did not try that. I suppose all files under /files1 and /files2 go to \windows directory just they happen to locate in different memory location in ROM

How do I integrate apps into the OS ROM for Wizard

I have been able to extract the EXT ROM and OS ROMs using the NB2NBF and IMGFS tools. I know that by using a custom ROM I can save on storage space by loading in my programs. I'd like to load Pocket Informat, Alarm Today, Phone Alarm , isilo and TCPMP into the OS ROM. How do I do this? I have all their cabs. I will keep reading the forums too.
I know that some like summiter have done this. Anyone able to help me get started or point me in the right direction?
J-Man5

the only device i ever heard supporting that is walaby
dont know if it's possible with other devices
i mean the os part of the rom is well you know full already

yes it is possibel.you need a tool called [typhoonnbfdecode_v5] look for this tool and how to use somehere in the ftp, and here in the wizard forums
you need to make a dump of the os from a nk.nbf image with the above tool
then you need to extract the files from de cabs you want plus the reg settings,
simply copy the extracted files from cab to your rom dump folder
make a cab file with the reg files from the cab files an also the shortcuts to the programs.
repack the rom with the typhoonnbfdecode_v5, convert the nba image with NB2NBF back to nbf and flash,after that install the cab with reg settings plus shortcuts,
you have a long jorney ahead.
i took me several weeks to make my own rom with netcf.2,adobe acrobat e several other programs integrated to the rom.

faria said:
then you need to extract the files from de cabs you want plus the reg settings,
simply copy the extracted files from cab to your rom dump folder
<snipped>
make a cab file with the reg files from the cab files an also the shortcuts to the programs.
Click to expand...
Click to collapse
OK I have gotten the nk.nbf extracted and the EXT ROM opened using winimage and the OS ROM dumped via imgfs.
Where I am running into problems understanding is how to unpack the .cab install files for the programs I am planning on using and how to "move" them to the \Program Files\ directories that they need to be in. For example PocketInformant is loaded into the \Program Files\WebIS directory. Do I put all the files from the .cab file in the dump OS directory? Is there some sort of program that will extract the .cab file and let me look at what registry settings are being set by its installation?
What program is used to create registry settings into a .cab file?
Thanks
J-Man5

BUMP

wincecab manager ,google it.

Hey!
I want to add some apps to the Rom of my Wizard, too.
I have used imgfs tools to great a dump from my OS.
Now i want to Install Total Commander to a Folder "\Programme\Total Commander\".
How can i do this? Or is it only possible to copy the files without any folder?
Sry for my bad english

To view & extract .nb0 content, please help......

hi all, i have a .nb0 file which extracted from a wm5 ppc phone ( cant remember the model), and i need some help here to view this nb0 and extract some cab file from there.
This .nb0 consist a lot useful softwares, for example, soundcover (background sound during conversation), answering machine, conversation recorder and it works flawlessly on wm5 ppc phone.
Any expert??? please help.
**ok, I found the phone model, its GIGA, this is the nb0 file, latest update from thier website http://www.higiga.com/HigigaFrontStage/event/download/update/V1.12.80.zip

Hi,
Congratulations on extracting an .nb0 file. There are many methods to do so, depending on the device. Out of curiosity, which method did you use? Assuming that you correctly extracted the .nbo file of the CE image, you can treat it the same as an .nb or .bin file. use "viewimgfs *.nb0". the * of course meaning the name of your nb0 file like MSFLSH50_2.nb0, or what ever. This will give you all the files and what not. You can then use the DSMtool by bepe. This will organize all the files into packages. Then you can use cabwiz or some other program to create a cab installer. Good posts to follow are mamiach, bepe, buzzlightyear, and others, if you didn't already know. The dsmtool is found in bepe's WM5 kitchen. the viewimgfs and other imgfs tools were created by mamiach.
Regards,
Jason

thanks for your reply, i will try to use the tools to see whether i can extract anything out of it...thanks again.

I think i have successfully dump the rom to a dump folder, but i cannot see anything but only some dll files, what else i need to do??? do i need to use some tools to convert all these dll files to view the rom content?? please advise, thanks.

[QUE] can not find Initflashfiles.dat inside dump folder

I dumped my rom that downloaded from Gigabyte official website using
Beta: WM5 ROM editing tool (mamaich tools)
Link to my rom:
Direct link
Everything should be ok! but I can not find Initflashfiles.dat inside my dumped folder. I want to remove some files from my rom to have some more space. According to posts in xda-developers after removing files I must edit some parts in Initflashfiles.dat.
Did any one face with this problem?
Is it possible to remove files and flash rom on my device without editing Initflashfiles.dat ? is it risky issue?
Thanks in advance

no one?

Did you uncheck "hide protected operating system files" for folder options in windows?

The initflashfiles.dat must be in there somewhere. Do a search on it and make sure you search for hidden files as well.
Psi