Can anyone please tell me what the difference is between NBF, NB0 and NB1 prefixed files.
I think NB0 is boot loader but what is this ?
NB1 is windows CE files, but what exactly ?
I am not sure what NBF files are, can anyone advise.
When you dump your ROM on a windows machine either using the wallaby bootloader or XDAtools is this ROM written as an NB0,NBF or NB1 file?
Thanks John
most things worth knowing is already right on this site
http://wiki.xda-developers.com/wiki/WallabyFileFormats
even seem to recall something about making fire with ones xda somewhere
Thank You Rudegar, I'll print off and peruse. You would'nt happen to know the answer to my other post ??
Thanks John
Thanks Rudegar you're a star
Thank you Rudegar you have help considerably. Even with my other post. Therefore when I back my ROM up from my device to my PC using XDAtools I must call this an NB1 file. I assume that in the event of problems that this NB1 file can be reloaded using the ProgrammeA part of XDAtools. If only I can get this to work I’d be a happy bunny. Hopefully someone will show me the error of my ways.
John.
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.
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
OK. I have extracted the the RSU from a t-mobile xda using the xda manipulator expert mode.
Now if only we could figure out how to convert it to an RSUpgrade.cp64 format, then we should be able to use the RSUpgrade.exe utility to flash the GSM rom with the converted file.
Does anyone know how to do this??? :?
Wade
Hmm.. I have no idea but I am in need of GSM ROM. I tried the usual flash method of RSUpgrade utility without any luck and left my xda useless...
can you share your GSM ROM file?
PLease share your GSM ROM file was readed from yout XDA.
I will tell you if there is any conversion to be made and how to.
thaks,
Silviu C
new ROM upgrade with radio_.nbf file
codectelecom: have you cheked this file: http://xda-developers.com/incoming/rom160wwe/RUU16006WWE_T-mobile_NL.exe
I tried to run the program but as usual got the POWER NOT PLUGGED IN error message due to our devices problems, but was wondering if you could study more as the programs consisted of 3 nbf files: ms.nbf, NK.nbf and radio_.nbf.
I extracted the files but was not able to write any of them to the SD card :? neither xda rit nor OSImage tools would accept the files. Is it because they are meant only for xda2?
HAPPY NEW YEAR, BTW
Anyone know how I can extract .nbf files? I need to see what is in this nbf file. Refer to this thread if you are curious
http://forum.xda-developers.com/viewtopic.php?p=250201#250201
Use the tools made by Buzz on this page:
http://buzzdev.net/index.php?option=com_content&task=view&id=65&Itemid=1
To see the contents of the nbf (converted to nba using the above method) file, you need to use these tools:
http://wiki.xda-developers.com/index.php?pagename=WM5EditROM
Its rather simple and hardly takes about 5 minutes for the whole thing
Cheers!
Thanx for the fast response. I gave it a go and it dosent seam to work. I get the .nba from the .nbf then when trying to
"prepare_imgfs.exe nk.nba"
I get this
"Searching for IMGFS start... Not found!"
I think that the .nbf is password protected. If anyone more gifted than me can help out with this one I know we will find a way to change the splash screen on all the newer (2.17 an so forth) ROMS.
Thanx again; Lew
then how do you extract NBF file from 8125 instead of NBA file ? Is there a way to do this ?
I would like input on this as well. I think we are missing a password here or something.
universaldoc said:
Use the tools made by Buzz on this page:
http://buzzdev.net/index.php?option=com_content&task=view&id=65&Itemid=1
Click to expand...
Click to collapse
I don't believe this works with (newer?) wizard nbf's.
Is there anyone here that could crack this would be "encryption" on the .nbf in question? I tried encoding my splash backup from aWizard using the project file from the "decoded" nk.nbf from "ruu_forcedalias_splash_245_425.exe" and it was a no go. It said that my storage was the wrong size for this ROM update (or something to the effect of NO). So it looks as if this nk.nbf from "ruu_forcedalias_splash_245_425.exe" is the key to unlocking the ability to change splash screens to custom images.
Later; Lew
u can try the tools in the attachment to extract files from image file.
the typho2 can extract parts from a SD card image, and the typhoonnbftool_04 can extract parts from a NBF file. they work well while do with the 1.x ROM, but I've never experienced it in extracting a 2.x ROM.
any exciting info, pls let me know,
Ok, good news, thanx to BrightMoonHeart I have been able to extract the BMP from the NBF using "typhoonnbftool_04.exe". The bad news is so far I can't seem to add an image (bmp) to the nbf or remove the current image. So this was a great step forward, just need a little help to get r done. I tried "typho2.exe" but I couldn't get it to do anything except give me the same info "typhoonnbftool_04.exe", It says it can extract the ".NBF" to an ".SPL" and that may allow us to edit it but I was not able to get it to convert. Any ideas guys? Always appreciated
Thanx; Lew
Ok I'm even closer now. I am using "typhoonnbfdecode.pl" and I can extract the ".nb" from the ".nbf". I can create custom splash using "nb_image_converter_859_418_826.exe" and make a ".nb" but when trying to put it back to ".nbf" i get this error
Code:
read 00030000 for splash from 92000000-Splash.nb
no sm signature at 0 in Splash
If anyone can help me out with any of this I would really appreciate it. I keep getting held up with all these conversions. I think some out there must know how to do this already, and I'm close but I keep hitting road blocks.
my head hurts; Lew
I have an iPAQ hx2790 (JPN) with WM5 and I was wondering if someone can point me in the right direction of extracting files from the ROM area. I did some searching and also looked at the WM5 ROM Tools thread, but I tried all these tools in vain. I tried dumping a ROM image from my ppc (using the tool that auto-dumps ROM into storage card) and extracting that but it didn't work (I believe it locked up). I tried dumping the original .nbf ROM upgrade file provided by HP but that didn't work as well. I just need to extract 3 .dll files so if someone can point me in the right direction, I'd greatly appreciate it!
You should decrypt NBF file, then the tools would work.
Currently there is no decryption tool available, you should make it yourself.
I don't remember the encryption used in HP NBF format, but it should be simple, maybe XOR with a constant string, and maybe some garbage added after each block.
Thanks for your reply mamaich, I didn't know HP's NBF was encrypted. Is there source code for a decryption tool someone made for another NBF format already?