Related
I just make the special edition ROM trhought mkrom and I obtain the.nb1 file, but when I flash my xd and make the cold reset, it hangs on the welcome screen, it print the 3 lines in red in the right bottom and after that ..... Nothing....... sniff
Anyone could help me????
I used the .nbf file that comes with the program A of O2.
Thks
that means that the windows kernel, and gsm have initialized.
the system should then proceed to execute the stuff mentioned in registry key HKEY_LOCAL_MACHINE\init.
maybe something went wrong with default.fdf?
I use the default.fdf that comes with the mkrom.zip, I just extract it and copy the nk.nbf file and proceed, I didn´t modify anything.
thks
I try to make another ROM with diferent Default.fdf but it hangs too.
it could be the NK.nbf file???
can you tell me where is a link fot one NK.nbf valid?
I´m going crazy :shock: jeje
thanks
if you use a different source rom, you need to change your default.fdf to
the one from that rom.
thanks for your patience,
I extract the default.fdf from the NK.nbf with dumprom.exe.
and then I use the fdf2reg.pl to create the default.reg and I put this file in the cfg directory, and after that I execute mkrom (sh mkrom.sh NK.nbf)
is that correct???
thanks
I think that the nbf file that I´m using is not a correct verion.
I tried to make a nbf file form jeff´s page but it doesn´t work with the nbf selection.
Do you know where can I find a nbf file that works with mkrom???
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
Hi all,
I finally decied to upload my modifed ROM in case anyone wants it. Its at:
ftp://xda:[email protected]/Uploads/pauls_modified_alpine_extrom_plus_radio104.zip
This is a ROM image which I modifed, using the O2 version 1.11.169 as a base.
Most of the O2 stuff is now gone, except for the battery meter and the
connection settings (WAP, GPRS, MMS, etc).
It includes my own startup screen. If you don't like this, please write to me
sending your own startup screen. Size must be 240 pixels wide by 320 pixels
high, BMP or NB format. When (and if!) I get time, I will make a new ROM with
your picture and send it to you.
The Radio ROM version 1.04 is also included. If you don't want to install
this, simply delete the "radio.nbf" file from the ROM image directory before
running the ROM update program.
The OS ROM is not included. Unless you've really screwed up your PDA, you wont
need this. If you do, just copy "nk.nbf" from another ROM update file into the
directory where you unpacked my ROM, before running the ROM update program.
There is a file called README.TXT within the zip archive which gives further information and lists the entire contents of the ROM file.
Any questions, feel free to contact me.
cheers.
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.