Hi,
Why OSImage Tool can't read nbf files?
try changing their extention to nb1 ?
ealtun said:
Hi,
Why OSImage Tool can't read nbf files?
Click to expand...
Click to collapse
Be sure you choose the right image file, OSImage Tools supports only image files for Wallaby Devices (O2 Xda, Siemens SX56...) it can read either nb1 or nbf format.
Related
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?
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
Is here somebody who can give me original or any ROM whitch is fit in to SX56 U.S.A. AT&T ? Model PW10B1 EN . This PPC is 10 days old. That's all I know about numbers :-( :? Thanks very much ! :!:
I have to reflash ROM with SD card.
www.yorch.net
www.yorch.net
cruisin-thru said:
www.yorch.net
Click to expand...
Click to collapse
Yorch's ROM Kitchen is not working
The kitchen is MIA, but if you click on the "upgrades" link you can find an original ROM image for AT&T. This is supplied as a .RAR compressed file. Open the .RAR file using WinRAR and extract NK.nbf that is located in the /English folder. You can use XDATools to copy NK.nbf to an SD card and install from the bootloader.
original ROM image for AT&T
pdhenry said:
The kitchen is MIA, but if you click on the "upgrades" link you can find an original ROM image for AT&T. This is supplied as a .RAR compressed file. Open the .RAR file using WinRAR and extract NK.nbf that is located in the /English folder. You can use XDATools to copy NK.nbf to an SD card and install from the bootloader.
Click to expand...
Click to collapse
Thankx much. Now i have everything i need but i have to go buy bigger SD card. My is only 32MB and that's not a enough Thankx again and i will let you know .
Unlock AT&T to ........
pdhenry said:
The kitchen is MIA, but if you click on the "upgrades" link you can find an original ROM image for AT&T. This is supplied as a .RAR compressed file. Open the .RAR file using WinRAR and extract NK.nbf that is located in the /English folder. You can use XDATools to copy NK.nbf to an SD card and install from the bootloader.
Click to expand...
Click to collapse
OK I fix the ROM problem and SX56 is like new, but is lock. I can't unlock it with XDAunlock. XDAunlock says : " error getting unlock code "
:-(
Now since you have the NK file of your favorit ROM, goto the kitchen again and upgrade to ROM 3.17 which will unlock your device with the first startup ... then you can reflash your device using the NK file.
I have Wm5 emulator which uses .nb0 file for running the ROM on the PC. Can any body tell me a tool for converting the .nbf to .nb0 files???
tried just renaming the extention ?
Yes I tried it already but to no help. There must be some tool to convert .nbf to .nb0?
This is a dumb question but what do you need to get .nbf files to your 8125 pda phone.
devilinabottle said:
This is a dumb question but what do you need to get .nbf files to your 8125 pda phone.
Click to expand...
Click to collapse
nk.nbf file is the OS (Rom) it requires a tool to flash it to a device which is RUU (RomUpdateUtility).A Rom is a complete compressed package,which includes OS(nk.nbf) and flashing tool RUU(RomUpdateUtility).Its the flashing tool RUU,which you execute to run the rom and flash it to the phone.
I presume you need to do alot of reading and understanding all these terminology and process of flashing