Hi
I have two questions :-
1. I know .nb0 and .nb1 files contain ,, but what about .nbf ?
2. Is these and XDA Developers own standard or is it HTC's ?
thanx
nb0 is commonly used for bootloaders.
we use nb1 for os images, not sure if anybody else does.
and I am even more sure that the .nb2 ( what we use for the diagnostics image ) is not used by others.
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.
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
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.
Hello developers,
maybe some people know, that there is a new TG01 section in this forum.
I personally own this phone and like it very much. Only the Rom that Toshiba provided us isn't very good and stable. It has many problems, that need to be solved
The friendly guys of WMPowseruser told us, that they want to try to cook a Rom for the Toshiba TG01.
But until now nothing happens, because nobody knows 100% sure what is needed to be done, to get a working Rom for the TG01 cooked...
So I decided to gain more information about the Rom Development process for WM-Phones.
I want to ask you what is needed to get a working cooked Rom for our Phone.
Do we need a Hard-SPL? Or do we need to extract the Rom out of our TG01, decrypt it so that we then can cook a new Rom?
You may notice, that I'm not an expert on this topic, so I rely on your help.
There is already a tool made by the member Cotulla to encode/decode TSW-files. http://cotulla.pp.ru/Misc.html
And it is also possible to flash every Rom that Toshiba provided us with this method:
http://forum.xda-developers.com/showpost.php?p=5405267&postcount=325
So it's possible to flash for example a german O2 Rom on an english TG01 that has the Orange UK Rom originally on it.
But I don't know if that helps us for our development.
We already gained 250$ for the development and I think that we're also able to gain even more money if it's needed!
We need serious help
I thank you in advance for your answers to this thread!
Every answer is welcome.
I also wish you a nice remaining Sunday!
Best regards,
Manuel
agree
TG01 have come to market for almost 1 year, hopping the cooked rom can be made early!
TG01
TGO1 MAIN bin file needs decrypted then it's full speed ahead
we need an experienced hacker
TG01
can the mods sticky this post we need it's full attention!!
Ok here is the acutal development status:
Progress of the Project WM6.5.3:
- With SDDL+ made by stepw we can flash any Rom on the TG01
- With Cotullas Tool we can decode/encode .tsw files
(The .tsw file is the file, that Toshiba offers to download from their homepage to update to WM6.5.3...so these .tsw files need to contain the whole OS and all system files that are needed to run the TG01)
Cotullas Tool can make a .bin file out of the .tsw file that we got from Toshiba.
But there are two problems with that:
1. We cannot be sure, that the Decoder works 100% right.
2. The .bin file we get when we use Cotullas tool seems to be not normal. We cannot extract it.
If I open it with Isobuster than I first see only the one track is included in the .bin file.
But then I let Isobuster search for more files after their signatures in the .bin file, Isobuster finds the following files:
00003808 , \Recovered File 01.mov
00112925 , \Recovered File 02.gz
00115498 , \Recovered File 03.png
00115530 , \Recovered File 04.png
00115533 , \Recovered File 05.png
00115563 , \Recovered File 06.png
00115791 , \Recovered File 07.cab
00115962 , \Recovered File 08.gz
00116325 , \Recovered File 09.png
00116351 , \Recovered File 10.cab
00116354 , \Recovered File 11.cab
00116385 , \Recovered File 12.cab
00116391 , \Recovered File 13.cab
00116417 , \Recovered File 14.png
00116420 , \Recovered File 15.png
00116421 , \Recovered File 16.gif
But for example the .cab files can't be extracted...it tells my, that the archive is damaged.
Well and we cannot be sure, that the above written files are the only content of the .bin file. Maybe Isobuster didn't find the others that are included in it...
So what we need:
- A person that understands the format of the .bin file (unencrypted .tsw file) so that we can extract the .bin file properly and get all of the system files and the OS out of it.
After that we can modify the files and create a new .bin file with the modified files included. Than we only need to encode it again, so that we have an flashable .tsw file again.
We could flash the new .tsw file with the SDDL+ made by the user stepw.
It would be very nice if someone would answer me and get in contact with me, that can help us to get a working WM6.5.3 Rom onto the TG01.
Thanks in advance!
I wish all of you a nice remaining Sunday evening!
Best regards,
DunkDream
hello,
to extract the rom, i used the raw-files.
i used "itsutilsbin"-tools. after dumping i get an extractet oem/sys-folder with known (typical) foldercontent and -structure.
here is a list of extractet raw-files
View attachment luste.zip
any lately news?
waiting...h
bird_9527 said:
waiting...h
Click to expand...
Click to collapse
The problem is in the nb0 file generated after using the cotulla tool.There are some extra bytes with checksum..i think only cotulla can make it possible.I tried manually with hexeditor..it fails..in short, we need another tool/program which can remove extea bytes, give us the normal nb0 file, which can be dumed recompiled and repacked with those removed extra bytes with the sme or modified checksum.Then we can have the custom ROM.