I am using cygwin and created a Rom using MKRom. The final Rom was 32,243,712 bytes or 31,488KB. When I tried to use the Upgrade.exe it got about 90% done and it bombed.
Fortunately, I was able to get to Wallaby and restore my original Rom Img. What went wrong?
Wade
that looks like the size of a nb1 file, not an nbf.
Related
Hi,
Just two questions.
1)I runned the Mkrom.sh and when building it it comes with the
error ' operator rom not found' but continues.
Then there's only a .nb1 file build which has a size of 32,243,712.
I don't know if this is correct !????
Is it a problem the operator roms are not found for a working rom???
2) Is it possible to delete, maybe even extract files from an image to
clean it so you get more space for your own programs?
hopefully any can answer these......
DCA said:
1)I ran the Mkrom.sh and when building it it comes with the error ' operator rom not found' but continues.
Then there's only a .nb1 file build which has a size of 32,243,712.
I don't know if this is correct !????
Click to expand...
Click to collapse
There should be both an nbf file of 32505888 bytes and an nb1 file of 32243712 bytes. So the size for the .nb1 seems correct.
Is it a problem the operator roms are not found for a working rom???
Click to expand...
Click to collapse
I'm not sure I understand the problem enough to be sure. Itsme, who made the tool, has left for a well-deserved two-week holiday, so I guess this will have to wait if you can't figure it out for yourself.
2) Is it possible to delete, maybe even extract files from an image to clean it so you get more space for your own programs?
Click to expand...
Click to collapse
Yes, extraction is possible using the dumprom tool described in another thread. Deletion of files to save space would take some hacking and slashing of your own. We do plan to make some more intricate ROM manipulations more easy once we clean up and publish more tools.
@XDA developer Peter Poelman
I'm glad the size is correct.
Just tried it again and only the .nb1 file is created, not the .nbf !!!
Is it possible to convert a .nb1 to a .nbf file??
Is the XDA ROM Tool able to write to USB SD-card reader/writers?
(could be an option to generate a valid .nbf)
thx
[ I split this topic away from the main Special Edition v1.1 thread, as it's not primarily about that. I will probably start doing this more as topics grow larger. ]
Yes, you can use XDArit to write an nb1 to SD, and then read SD to nbf. Easier tools for this exist, and we've even built the beginnings of one (which we haven't yet released).
If you have the SD, you could also just use the bootloader to burn the contents to flash.
Can anybody please help me to build a rom? specially to the XDA-developers, thanks in a million...in advance.
My question is:
1. Do i need a base rom(no program included) on the cfg/(rom.nb1)? is it necessary ?
2. what is the maximum files i can put in the files/ directory? that will be splited by mkrom, i know it is depending on the version since 3.17 the maximum for all files is 5 M. how about other version. 4.01,4.05, 4.10 and 4.16
3. when i run the bash setup.sh nk.nb1(4.05), using parameter for 4.05 i get a message "!!! your rom is not known to me: md5:fb9e70c5786f08e4db6db7c184c59704" is this normal or it is not define on the splitrom.pl ?
4. what kind of editor did you use for building a BMP file with 16 bit, I tried to use adobe photoshop 6.0, but i can not seem to save it as 151 k, the option is only 24 bit and 8 bit, if you can give me a site where i can download it , i will really apreciate it.
Thanks for the Help..
More power to the XDA team
and
Welcome TMO 4.16!!! (which i think no diff with 4.10)
1. yes you do need some kind of rom to start with
2. you can check using
Code:
perl splitrom.pl yourrom.nb1 -ob <your bmp offset> | perl calcgaps.pl 0x3ffff
and add the sizes of the holes.
you have to figure out where the bootsplash is for your rom. ( for new roms this is most likely 0x81ec0000 )
3) there is a list of 27 roms I know about in splitrom, if I never saw your rom, the signature will also not be there.
btw, what rom do you have?
4) I think we used photoshop for that. ( Peter Poelman knows more about that )
thanks for the reply XDA developer Itsme,
but how can i build a baserom with the rom i have, I have a ROM 4.05 which i created in jeff's kitchen? or any site where i can download the base rom 4.05?
I have a ROM 4.05, 4.10 which i get from jeff's kitchen and also the original 4.10 TMO. regarding the signature of the ROM, i read your splitrom.pl and i found out you 27 list of roms, but i didn't find that signature "md5:fb9e70c5786f08e4db6db7c184c59704" is it because my ROM is not base ROM?
my param is ;
wincever=4
start1=21740000
size1=0040000
start2=003c0000
startbmp=81ec0000
startop=81b00000
I'll still try to use the photoshop, maybe i miss something there.
Please correct me if i done something wrong with my commands.
I have Perl 5.8 and cygwin, installed in windows 2003
then make the path for perl/bin and cygwin/bin
then i copy all the things i need to build a rom in one directory including nk.nbf(with jeff's 4.05) and mkrom tools(which i got from the demokitchen)
i run "perl setup.sh nk.nbf" to extract the bootimage.bmp and rom.nb1 to cfg/ directory
then i dump "dumprom -4 -d files -q nk.nbf" to extract all files in files directory
then i convert "perl fdf2reg.pl files/default.fdf cfg/default.reg"
"tr -d "\0" <files/initobj.dat >cfg/initobj.txt"
"cp files/initdb.ini cfg/initdb.ini"
then in files/ directory i delete all the windows files i leave only the program with the dll i wanted to add in the rom like total commander, file commander.. etc...
(I compare it with the original files of WM2003)
then i run "bash mkrom.sh out/out.nbf"
but i got an OVERLAP message on the screen
and also the same message like i told you before "Your rom is not know to me"
Please Help me with this because i want to build my own rom according to the program i need.. and many thanks.
split rom does not recognize romkitchen roms, since they vary too much.
you should use an original rom, not one from the romkitchen.
the overlap means that somehow the params file was not correct.
or maybe you just tried to add too much files.
XDA developer Itsme said:
split rom does not recognize romkitchen roms, since they vary too much.
you should use an original rom, not one from the romkitchen.
the overlap means that somehow the params file was not correct.
or maybe you just tried to add too much files.
Click to expand...
Click to collapse
Thanks Itsme, thats why splti rrom can not recognize the ROM I have, I'll try to search for the base ROM in the forum, or can you give me a site where i can download the baseROM, I think that's why I am having a OVERLAP because there is a added program on my ROM, XDA-Developers File1 and File2 is duplicated.
It answer my question regarding the ROM i have, thanks a lot man you really a good help.
Now my only problem is to find all the base rom so i can start cooking some ROM.
after I cooked ROM from Jeff Summer's Kitchen, it has the option to choose whether you want it .nb1 or .nbf
.nb1 is for SD card flashing
while .nbf is for advanced users...
so what is exactly the difference between this 2 extensions??
Good Q - I was finkin that 2
Keen to always b learning more. Would appreciate a response to add 2 d knowledge for which without this site I would be stuffed wit an XDA still stuck on d update screen
an nbf file contains some information about what kind of device the os image
is intended for, and a bootloader and the os image.
a nb1 file contains only an os image.
nbf's can be flashed with Programme A.
see http://www.xs4all.nl/~itsme/projects/xda/wince-flashfile-formats.html
osimagetool understands both nb1 and nbf files.
XDA developer Itsme said:
an nbf file contains some information about what kind of device the os image
is intended for, and a bootloader and the os image.
a nb1 file contains only an os image.
nbf's can be flashed with Programme A.
see http://www.xs4all.nl/~itsme/projects/xda/wince-flashfile-formats.html
osimagetool understands both nb1 and nbf files.
Click to expand...
Click to collapse
Do you mean if I flash the phone with .nbf via osimagetool ( Programme A) , it could be over-write bootloader ?
yes, it could. but osimagetool will not take the bootloader from the nbf,
it always puts the 5.15 bootloader in the file that is flashed with "Programme A"
for a reason I don't yet understand, the bootloader is not always updated.
I am quite sure that "programme a" used to update bootloaders, but I have not seen it do this for some time. - maybe it has to do with the rom version?
I have been looking for a mkrom that works with 2003 ROMs. since kitchen cooks 2003 rom, there must be one version of mkrom that works with 2003.
I downloaded the kitchen, and tried to use the small set under one of _/ directory to cook my version of 2003 without setting out the entire kitchen. but got into one problem. -- the xda does not boot
it shows the boot screen, and the G324e4, R6.10.00 4.00.11, then stops there
one thing I figure went wrong is:
the default.reg I got out of default.fdf is oly about 30k large while the old 2002 version of default.reg is more than 200-300 k large.
any one can help here? I cooked based on 4.00.11 rom, which by itself installs on my xda fine.
Hi Pine
If you are trying to add files to you're Rom you will need to use an original (Not one from Jeffs Kitchen) as the XIP segments get screwed if you try to re-write them. (not sure why) If you run Mkrom without adding additional files you will find it loads fine.
Richard
I was not trying to add my files at all. I downloaded a rom, followed the step to cook a new rom without adding any of my files. the resulted rom does not load. quite disapointing experience.
I used the 4.00.11 rom, used the 4.00.11 directory in the kitchen download, modified mkrom to comment out the wince 3 version variables and uncomment the 4 version variables.
anything else I should do?
or the kitchen downloaded from xda-developers.com does not actually work with 2003 yet?
O.K.
Rom Kitchen contains parts of the old Mkrom but relies on more perl scripts to do the work. I have done the same as you and it works fine for me. Best guess is you havn't converted the the default reg properley did you use tr -d "/0" <default.reg>default.txt to convert ? check that you can actualy read the output if its in hex then youv'e done it wrong. The output file should be around 8 to 12 kb
Richard
you can find the most recent version here
anyone know how to flash ROM using .nb0 ROM file?
Toshiro said:
anyone know how to flash ROM using .nb0 ROM file?
Click to expand...
Click to collapse
Yea you can do it with the XDATools program!
For more info. on XDATools read:
http://xda-developers.com/forum/viewtopic.php?t=2189
Download site:
http://cuba.calyx.nl/~jsummers/XDA/XDAtools-Jeff.exe
HTH
normally an .nbo extension means that the file is the bootloader part, not the Windows CE part.
An .nbo file should hae a size of 256 k, while an .nb1 file is around 32 meg.
my .nb0 file size is 32 MB
I normally have an aversion to blindly changing the extension on files, especially when they are going to be used in a ROM upgrade, but I think you want to change the extension to .nb1. I would suspect that the bootloader wouldn't know what to do with a 32 meg .nb0 file.
i'll try that... thanks
you may also want to check your file using 'splitrom.pl'
it will try to determine what is contained in your file.
to be safe, convert it to a 'sure' nb1 by typing
Code:
perl splitrom.pl yourunknownfile.xxx -wo truenb1.nb1
i'm not familiar with perl scripts and i don't use linux
i'm using win xp
is there a way to do this using win xp?
thanks
Qman... I tried using XDAtools and it didn't work. OSImageTool didn't recognize the file's format.
Any thought?
Toshiro said:
Qman... I tried using XDATools and it didn't work. OSImage Tool didn't recognize the file's format.
Any thought?
Click to expand...
Click to collapse
Thats real strange I just copied an image with the same extension to a SD card without any problem, oh wait I used XDArit 1.0 and not XDATools.
So I'll give XDATools a try when I get off work tonight and post how that went.
BTW the file I used was a boot loader backup ROM and then I used XDArit to copy it from the SD card to hard drive and I named/saved that file as xdarom.nb0 then I used XDArit to write it back to the SD card, bingo no problem!
BTW Toshiro thats why I had ask you to send a copy of that file to see if I could write it disk, but since you didn't I just created one myself and it worked. :wink:
Can somebody else give this a try and see if it also works for you.
HTH
Toshiro:
i'm not familiar with perl scripts and i don't use linux
i'm using win xp
is there a way to do this using win xp?
thanks
Click to expand...
Click to collapse
Activeperl.