Database Users

What's wrong with the SE ROM??

After downloading Jeff Summer's rom (.exe file), I tried clicking on it to extract the files...no good.
Then I used Winzip and extracted to C:\windows\temp.
Next I click on start.bat and the dos window comes up stating NBF directory not in the C:\windows\temp directory?
I move the nbf file to this directory and the uprgrade process starts.
Next I get Error 012
"Rom image that you are trying to upgrade is not compatible to your Pocket PC.
Your device
ModelW10B1
Rom version 3.14
Lang: english
Your upgraded image information:
ModelW10A1
Rom version 3.17
Lang: english
Please download comaptible utility."
What the hell went wrong??
:? :?

Sound like you extracted everything in one directory instead of in the directories mentioned in the self-extracting exe. Or something similar.

Not exactly. Here's what I did as best as I can remember.
When I clicked on the .exe file, a dos box opened, gave me an error message that it could not find the nbf directory.
Then I used winzip to extract the files into the same directoy as the .exe file.
From there I tried running the start.bat file. Still no good.
What finally worked was a strange combination of clicking on the .exe file and then immediately clicking on start.bat. This was after I moved the nbf file from the \english subdirectory to the subdirectory that had the .exe file.
It was a strange work around, but it work and the rom loaded and seems to work well.

I am getting the same problem here but I havent been able to work around it. I tried what worked for you without success.

Extract Files from ROM???

Does anyone know if there is a way to extract files from ROM? Since we can add files via MKROM is there a way to either extract files from the ROM or the .nbf or .nb1 files?

yes, just use the dumprom utility but remember you wont be able to pack them all back in for the compress.dll is not being utlized yet.
You can get dumprom for win32 here http://www.xs4all.nl/~itsme/projects/xda/dumprom.html
Dont forget dumprom can extract files from 4.x roms with the '-4' commandline option.

What I would like to do, if possible, is to extract the files that makeup IE in the 4.00.10 version and then load them into an SPHi700 running the 2002 ROM. Then change the registry keys and see if it will work. It appears that there are only two files required though there might be more. If it needs API calls and entry points in the OS that are not there in 2002 then it wouldn't work. Otherwise I would have an upgraded IE in the 2002 SPHi700.
Any idea if I can do this and if it will work?

Hi Barjohn. Thanks for the info regarding the "g" and I have found a rom of .05 that it works with.
As far as taking IE from .10 to ppc2002 I don't think it will work. The architecture appears to be different, as well as the registry structure. Something like Win98 to WinXP.
Just my .02 but that is what I have been reading online.

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

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.

[TOOL] Extract CAB/BIN files from EXE v1.10 (Unpacks HTC Roms/Hotfixes, Omnia ROMs)

Description
Takes an EXE file and extracts the contained CAB or BIN files (the file is trimmed to match the internal size). It can extract:
1) the CAB that contains the ROMs in the HTC ROM Updaters from which you can get the NBH/NBF ROM file.
2) the CAB contained in the HTC ROM Hotfixes that you can after cook in your ROMs or install on your phone without using activesync
3) the BIN in the Omnia i900/i910 ROM Updaters for XP/Vista (and maybe some other updaters)
How to use
Drag&drop the file you want to scan on the tool executable and if the file is detected it will be extracted in the folder. This is a command line tool so if you want to see the output you will have to open it in a command prompt.
Changelog
(NEW) v1.1: Added support for the Samsung i780 and other updaters that contain the .bin file uncompressed inside
v1.0: Initial Release

thanks
thanks bro will try this......

Great Tools, thanks!

maybe stupid but isn't that the same as renaming the .exe to .rar and then extract ?

So will the new 1.31 Kitchen work with .bin files from Samsung i780? I guess you could use this tool to extract the bin from the .exe updater. And does the kitchen import the .bin file just like a .nbh?
I have a i780 that I use for daily phone use. I don't flash it very often. The current ROM is one I built a long time ago using old building methods. One of the reasons I don't want to cook a ROM for it is it's too much work. Lol

Great tool. Thanks for shared...

ceesheim said:
maybe stupid but isn't that the same as renaming the .exe to .rar and then extract ?
Click to expand...
Click to collapse
When you use winrar or 7-zip to unpack the files they will only extract the content of the CAB archive making hotfixes useless and when you use osnbtool to extract the file from the Samsung updaters it will return you a trimmed NB0 file instead of the original BIN file that you cannot directly flash. My tool scans the files and gives you the intact CAB/BIN files without any further processing.

bobsbbq said:
So will the new 1.31 Kitchen work with .bin files from Samsung i780? I guess you could use this tool to extract the bin from the .exe updater. And does the kitchen import the .bin file just like a .nbh?
I have a i780 that I use for daily phone use. I don't flash it very often. The current ROM is one I built a long time ago using old building methods. One of the reasons I don't want to cook a ROM for it is it's too much work. Lol
Click to expand...
Click to collapse
The i780 has a BIN imagestart different from 0 meaning a bootloader or other stuff could be present so I wouldn't even dare flashing anything that the kitchen produces without a custom batch file. This tool cannot import the i780 files because it looks for the omnia imagestart that is 0.

airxtreme said:
When you use winrar or 7-zip to unpack the files they will only extract the content of the CAB archive making hotfixes useless and when you use osnbtool to extract the file from the Samsung updaters it will return you a trimmed NB0 file instead of the original BIN file that you cannot directly flash. My tool scans the files and gives you the intact CAB/BIN files without any further processing.
Click to expand...
Click to collapse
cool , thanks for explaining .

Thanks airxtreme!!!! This is one more amazing tool to add to the collection.

Thanks Bro Great app

Awesome tool airxtreme....thanks for sharing.

airxtreme said:
Description
Takes an EXE file and extracts the contained CAB or BIN files (the file is trimmed to match the internal size). It can extract:
1) the CAB that contains the ROMs in the HTC ROM Updaters from which you can get the NBH/NBF ROM file.
2) the CAB contained in the HTC ROM Hotfixes that you can after cook in your ROMs or install on your phone without using activesync
3) the BIN in the Omnia i900/i910 ROM Updaters for XP/Vista (and maybe some other updaters)
How to use
Drag&drop the file you want to scan on the tool executable and if the file is detected it will be extracted in the folder. This is a command line tool so if you want to see the output you will have to open it in a command prompt.
Click to expand...
Click to collapse
I've tried to extract files from a HTC Rhodium FaceBook Hotfix but it returned with "no files found". Just to confirm that your tool was not designed to do that?
Hotfix is attached for your reference. Thanks.

zard said:
I've tried to extract files from a HTC Rhodium FaceBook Hotfix but it returned with "no files found". Just to confirm that your tool was not designed to do that?
Hotfix is attached for your reference. Thanks.
Click to expand...
Click to collapse
The archive is truncated indeed it doesn't even have an icon like HTC hotfixes usually have. The tool won't extract it because it the archive integrity is checked before extracting the content.

I uploaded a new version with Samsung i780 (and potentially other older samsung phones) ROMs support if anyone is interested.

airxtreme said:
I uploaded a new version with Samsung i780 (and potentially other older samsung phones) ROMs support if anyone is interested.
Click to expand...
Click to collapse
If posibble please make support for the latest samsung updater *.exe.
Because i think the newest samsung updater .exe like sprint intrepid have diferent structure, not like older updater *.exe that can be extracted the bin file by manualy triming the unused bytes with hex editor or with your great tools..
Thank you..

nice little app, added to my toolbox. thanx