Related
Hi XDA-Developers!
First of all: you did a really great job and thanks a lot for ROM 1.1!!
I just want to ask you to explain initobj.txt, files1-dir and files2-dir a little bit more, so i can make my own ROM, and maybe a german ROM.
i'm little bit confused with the format of initobj.txt corresponding to the files in dirs files1 and files2. not every file in the file dirs is listed in initobj.txt. Why? How are these files arranged in the filesystem? ie. how do your scripts know where to put 'vxutil_cl.htp' - it's not in initobj.txt in cfg.
Maybe you could explain it a little bit more....maybe there is already some manual beside 'readme' ???
Thanks a lot.... Jabba
all files in rom can be found in the \windows directory. the initobj.txt files specifies for certain files that copies to other places should be made..
so if a file is not mentioned in initobj.txt, it is only visible in \windows.
also the name of a file in \windows does not nescesarily correspond to the name in wherever it was copied to by initobj
initobj.txt has 2 types of lines ( there are more, but I never looked at them )
Code:
Directory(..dir..) :- Directory(...subdirname...)
to create a subdirectory in 'dir'
Code:
Directory(..dir..) :- File(..filename.. , ...source...)
creates copy of 'source' as 'filename' in directory 'dir'
the reason there are 2 'files' directories, is that there are 2 empty spaces in the rom (1M before the bootsplash, 5M after the bootsplash). I could have made the mkrom script more advanced, and have it automatically figure out how to optimally sqeeze files in either space 1, or space 2. but I didn't , so I'll leave it to the rombuilder to decide how large to make each region.
thanks for your answer!
will it be a true copy from source ? I mean will there be two identical files in the rom then or is it more like a link to the source-file?
another question: is there something in your scripts which is language-dependant ? like the altered welcome.exe ??
in the german rom there are some dirnames different - so i would have to alter the reg-file and the initobj to fit them. Do i have to alter other files as well? Like operator or the welcome.exe ?
Jabba
By the way, would be developers so kind to explain the ways how to extract initobj.txt and default.reg files from the ROM? Or perhaps "original" Qtek ROM files could be published?
I would be of a great help in my ROM-building...
thanks
we based everything on an english qtek rom. if you start with a german rom, you will have to pay attention to differing directory names.
you can get initobj.txt from initobj.dat, by converting the file from unicode
to plain ascii. I usually load it in vi, then do ":%s/^@//g" to strip all NUL characters, and then save it as .txt.
the default.reg you get by converting 'default.fdf' found in the rom, with
Code:
perl fdf2reg.pl default.fdf default.reg
and I wrote this tool (bottom of page) to extract files from a rom image. for most roms you type
Code:
dumprom nk.nbf -d files >nkinfo.txt
to extract the files to the directory 'files' ( which must exist ), and dump lots of info about the rom to nkinfo.txt
The Rom Koch at the moment does not support .nb files that have been created with tadzio's ImgFsTools as of now.
I've been wondering if we can perform the following steps to rebuild the .nb file using mamaich's old ImgFsTools.
If we can repack the dump into a rom that still has the 8Mb space in it, it should be possible for Rom Koch to open the file without problems. We can, after modifying that rom, repack it with the new ImgFsTools to shrink the files again.
I have been trying a couple of ways to do this, but run into some problems along the way. I've been digging in the forums to find out what I'm missing here, but can't seem to figure it out. I might be doing something totally obsolete here, but I've seem numerous posts of people trying to customize one of the precooked rom's with the Rom Koch, and didn't get anywhere.
First Try: Just unpack the .nb and repack.
Using the old ImgFsTools, I immediately get errors that there are invalid headers in the file doing the prepare command.
Second Try: First use NbSplit, then unpack and repack the payload.
This one neatly packs the payload again using the old toolkit, but after NbMerge on the files, the file is still small. So apparently it's not just the image file that has lost some size, because that is packed using the old tools, and should include the 8Mb free space. Seems like I'm mixing things up here, so have to try this another way.
Third Try: Same as above, but when repacking, use a different template.
I follow the steps that give me a smaller .nb file from the second try, but when repacking, I provide a both the old and new toolkit a template file of a fixed size rom. This packs the smaller rom data in a 67 Mb .nb file, so looks promising. Rom Koch still throws a DivideByZeroException though, so while I got (my test rom) the Black V2.0 rom in a 67Mb .nb file, that's not the problem.
Am I trying something remotely possible here, or should we just wait for an updated version of the Rom Koch to customize the precooked roms? Obviously, the new ImgFsTools do a lot more than just creating a smaller .bin file.
wait for koch v2.
It can be done and I've done it before using Jasjamming method.
Steps:
1. Prepare a good untouched version of any WM6 rom version ( No free space tweak by Tadzio's Toolchain) - Will be used as shell rom
2. Dump the WM Black 2.0 rom using Tadzio's toolchain only ---> Dump folder will be created: Do not delete
3. Use aWaiter and make imgfs_raw from the rom taken from no. 1 : Do not delete
4. Use normal imgfs tools to compile the dump directory using the imgfs_raw from no. 3 (Shell)
5. Make a new .nb file with the size of 67.7 MB.
actually guys... it's simple.
take an NB, split it into the dev data and the payload.
take the payload, and dump it... play with it, whatever, but remember to re-merge after you're done.
Olipro said:
actually guys... it's simple.
take an NB, split it into the dev data and the payload.
take the payload, and dump it... play with it, whatever, but remember to re-merge after you're done.
Click to expand...
Click to collapse
Sounds great, but I am waiting for Koch 2 that is even easier
Thanks guys, I guess I've been thinking too hard on this one.
Just wanted to try this to conveniently experiment with the precooked roms, but I guess convenient is when Rom Koch is upgraded...
I'll give the above suggestions a shot.
Does anyone know how to make custom roms for devices like the Excalibur or other Smartphones. I want to remove a lot of the clutter and add some applications of my own.
JAmerican
Not there yet AFAIK.
The closest I have gotten is extracting the rom components and mixing them. I took the HTC Splash, the HTC Radio, and the T-Mobile OS; made a custom ruu and flashed successfully. Now my Dash shows HTC Screen when it boots and I have the updated Radio. I managed to dump the T-Mobile OS, but haven't been able to rebuild. HTCRT by Dark Simpson will create the ruu_signed.nbh for use with the uspl though. NBHEXTRACT will break the nbh into its components. Tried the HYPERCORE tools, that's how I got the dump of the OS, but cannot do the xip parts with these tools for some reason. PKG Tool works. Have the OEM and SYS folders, but XIP comes up empty.
This is something I hope to see... I mean why even bother with getting the HTC unbranded version if we can remove all the clutter ourselves?
momentarylapseofreason said:
This is something I hope to see... I mean why even bother with getting the HTC unbranded version if we can remove all the clutter ourselves?
Click to expand...
Click to collapse
Bug fixes! Even if you build a custom rom, you would want to start with the latest available OS to get in on whatever bug fixes have been added. Then you would rip it apart and add/remove whatever you wanted. Sometimes the new OS would also have added/improved features, but the bug fixes is the main one.
mar11974 said:
The closest I have gotten is extracting the rom components and mixing them. I took the HTC Splash, the HTC Radio, and the T-Mobile OS; made a custom ruu and flashed successfully. Now my Dash shows HTC Screen when it boots and I have the updated Radio. I managed to dump the T-Mobile OS, but haven't been able to rebuild. HTCRT by Dark Simpson will create the ruu_signed.nbh for use with the uspl though. NBHEXTRACT will break the nbh into its components. Tried the HYPERCORE tools, that's how I got the dump of the OS, but cannot do the xip parts with these tools for some reason. PKG Tool works. Have the OEM and SYS folders, but XIP comes up empty.
Click to expand...
Click to collapse
Thanks for the insight. I reached as for as extracting the .NBH into .NB files with OS, GSM etc. How do you extract these. The PKG Tool didn't work for me and the Hypercore tools aren't working right either.
JAmerican
Hey all,
I was able to downgrade to WM5 and I am starting to understand a few things regarding ROM building but I still don't know how to edit the Windows.nb or OS.nb file. Can anyone offer suggestions. I am trying to optimize it so that there is less clutter.
JAmerican
I was able to extract the the OS.nb before and edit it, but unfortunately, it was not fully extracted as i was hoping, at first i thought i was able to fully extract it, but when i tried to reflash again the OS, it was flashed normally but not as functional as normal one, many were not included, the Start Menu seems to be incomplete, no keypad lock, no quickapp etc... so i came up with a conclusion that it was not fully extracted..even the initflashfiles.dat were not present on the dumped files, i thought that file was the only one missing and i tried to manually copy it from /Windows/ directory and put it on the dumped files folder..but it wasn't a success.
Anyone successful to fully extract the OS? I'm slowly compiling a kitchen for Excalibur and the full extraction of the OS is only the missing part of the kitchen and i'm stuck with it. Once it is up and found a solution, then we can come up with cooked roms for Excalibur.
da_mayhem said:
I was able to extract the the OS.nb before and edit it, but unfortunately, it was not fully extracted as i was hoping, at first i thought i was able to fully extract it, but when i tried to reflash again the OS, it was flashed normally but not as functional as normal one, many were not included, the Start Menu seems to be incomplete, no keypad lock, no quickapp etc... so i came up with a conclusion that it was not fully extracted..even the initflashfiles.dat were not present on the dumped files, i thought that file was the only one missing and i tried to manually copy it from /Windows/ directory and put it on the dumped files folder..but it wasn't a success.
Anyone successful to fully extract the OS? I'm slowly compiling a kitchen for Excalibur and the full extraction of the OS is only the missing part of the kitchen and i'm stuck with it. Once it is up and found a solution, then we can come up with cooked roms for Excalibur.
Click to expand...
Click to collapse
Cool. I went back to WM5 to see if it was more efficient but with all the lack of features (email instant search, alpha-dialing, file syncing, etc.) It was not worth it. I went back to WM6. I hope we can get some cook ROMS soon. I really want more usable RAM. Could you give me the exact steps you used to extract the ROM? I tried HyperCore but it doesn't work for me for some reason.
JAmerican
JAmerican said:
Cool. I went back to WM5 to see if it was more efficient but with all the lack of features (email instant search, alpha-dialing, file syncing, etc.) It was not worth it. I went back to WM6. I hope we can get some cook ROMS soon. I really want more usable RAM. Could you give me the exact steps you used to extract the ROM? I tried HyperCore but it doesn't work for me for some reason.
JAmerican
Click to expand...
Click to collapse
Try this mate:
Aserg's Imgfs Tools, attached on THIS thread
Place OS.nb on the same folder then execute !UI_wwe.cmd
Choose P - Unpack OS.nb <for Herald-Prophet> to dump-folder
the ROM will be dumped on the "dump" folder, but i don't think it's a complete dump, if there's anyone knows how to do the complete dump, please share
da_mayhem said:
Try this mate:
Aserg's Imgfs Tools, attached on THIS thread
Place OS.nb on the same folder then execute !UI_wwe.cmd
Choose P - Unpack OS.nb <for Herald-Prophet> to dump-folder
the ROM will be dumped on the "dump" folder, but i don't think it's a complete dump, if there's anyone knows how to do the complete dump, please share
Click to expand...
Click to collapse
Thanks for sharing! I was finally able to dump it. Now to see if I can mess around and get it to build! Wish me luck .
JAmerican
You can easily build it again, but the question again is, are the files on the dump folder complete? i wish you luck mate! keep us posted.
da_mayhem said:
You can easily build it again, but the question again is, are the files on the dump folder complete? i wish you luck mate! keep us posted.
Click to expand...
Click to collapse
I deleted some files from the ROM and rebuilt it but it was in .NBA format. I don't remember exactly what I did but I think I renamed the file to .NB and made a .NBH file out of it. Then Flashed my device. I got as far as the WM screen and was stuck there. I reflashed with the Standard WM6 ROM from T-Mobile. .
I'll try some more messing around. I really want to get some cooked roms for Smartphone edition.
JAmerican
Your right about files missing. I was able to extract the ROM and its packages and get two folders (ROM and SYS) along with other packages. The program I used (Package Tool) states that I am missing the following files:
[Missing Files]
SYS\MSXIPKernel
MODULE: busenum.dll
MODULE: cachefilt.dll
MODULE: certmod.dll
MODULE: coredll.dll
MODULE: device.exe
MODULE: devmgr.dll
MODULE: diskcache.dll
MODULE: encfilt.dll
MODULE: fatfsd.dll
MODULE: fatutil.dll
MODULE: filesys.exe
MODULE: fsdmgr.dll
MODULE: fsreplxfilt.dll
MODULE: hd.dll
MODULE: imgfs.dll
MODULE: mspart.dll
MODULE: osaxst0.dll
MODULE: pm.dll
MODULE: regenum.dll
SYS\WinCENLS_WWE
File: wince.nls
OEM\LangDB
File: initflashfiles.dat
File: mxip_lang.vol
OEM\OEMXIPKERNEL
File: boot.hv
File: boot.rgu
MODULE: cecompr.dll
MODULE: ceddk.dll
MODULE: HtcFsdspy.dll
File: mxip_initdb.vol
MODULE: nk.exe
MODULE: ONDisk.dll
and these files are in the Windows folder as well as other locations on my device. The only problem is that the device denies me access to these files. Is there a way to access these DLLs with a powerful file manager. I tried Resco and Total Commander to no avail. Anyway to trick the device into allowing me to copy these files?
Thanks.
JAmerican
I believe there is a need for a simple ROM cooking procedure on devices such as Excalibur and Vox. I'm thinking of a "Norton Ghost" procedure to backup and restore the entire OS and User Filesystem partitions.
The ROM cook procedure would then be something like this:
1. customize the device (all changes stored on device memory of course)
2. backup OS partition (using special USPL)
3. backup User File System (using special USPL)
And a user would just do this:
1. restore OS partition (using RUU)
2. restore User File System (using RUU)
3. personalize device
Does that sound acceptable?
Ok so I was able to extract the T-Mobile WM6 ROM, I was able to use the Package Tool to get it seperated into a SYS and OEM folder. I deleted things like Live Messenger and Windows Live. I put the updated version of Live Search in ROM. I only added one other application, CeleTask. I didn't want to put too much work into tweaking this thing and find it not working. I am downloading the CreateOS.exe and CreateROM.bat files and will try to compile this thing. Wish me luck.
JAmerican
jockyw2001 said:
I believe there is a need for a simple ROM cooking procedure on devices such as Excalibur and Vox. I'm thinking of a "Norton Ghost" procedure to backup and restore the entire OS and User Filesystem partitions.
The ROM cook procedure would then be something like this:
1. customize the device (all changes stored on device memory of course)
2. backup OS partition (using special USPL)
3. backup User File System (using special USPL)
And a user would just do this:
1. restore OS partition (using RUU)
2. restore User File System (using RUU)
3. personalize device
Does that sound acceptable?
Click to expand...
Click to collapse
Hey friend. I know this is not appropriate place to post this, but since you know my situation on the wifi of my phone. Would it be possible to put a working reverse flash of a tmobile dash onto mine and fix the wifi. I have tried everything. And you have been very helpful and it is much appreciated.
keep up the progress guys, i can't wait to try some of the cooked roms from users on this site
Good luck, i can't wait either....
Hey guys,
I used a tool to try and convert my unpacked ROM back to a packed (one folder ROM) and it deleted all my progress. Go figure. So I have to basically start all over again. This time though, instead of making all the changes. I am just going to remove like myFaves, update LiveSearch and add one of my own applications as well as one of my favorite applications and see if I can flash my Dash with it.
Somewhat but its my fault for not backing up.
JAmerican
I am planning to use the Core/Hypercore and/or Pandora's Kitchens to play around with the latest AT&T ROM.
The following is something that has always confused me to some extent in the past.
If I want to delete or change the files that are part of any particular package, I imagine that I need to create a new .DSM file to go along with the changes/deletions I might make.
The HyperCore kitchen provides a utility to rebuild the .DSM file, but from what I can see, the new .DSM file created is nothing like the original. It seems to be lacking a lot of binary information that exists in the original...prior to the file listing.
First...Is it safe to NOT create a new .DSM file if I simply want to delete files from a particular package?
Second...If I merely change some icon/bmp resources in any of the files, and the name remains the same...do I need to create a new .DSM for that package?
And finally...as there seem to be differences between existing .DSMs and the ones that are created by the Core utility, can I really trust the new ones I generate?
Any help/guidance would be appreciated...thank you.
-pvs
PLEASE NOTICE THAT THIS KITCHEN IS A VERY EARLY BETA AS IT HAS NOT BEEN DEEPLY TESTED
*** USE IT AT YOUR OWN RISK! I ASSUME NO RESPONSIBILITY! ***
Hi guys,
after many days of testing I'm releasing my kitchen for i780.
It is very basic: no gui, only batch Windows scripts.
What you can do with this kitchen:
A) Convert your Part02.raw dumped rom to bin flashable PDA rom
B) Create a dump folder to cook your own rom and recreate a bin flashable PDA file.
Please notice that there's no tool included to edit, add or delete modules and files from rom dump.
You must use one of the tools available here in forum to do this or do this by hand.
Donwload the zip file and extract everything.
READ CAREFULLY THE README FILE IN THE ZIP ARCHIVE
This file explains how the procedures work and what you need.
PLEASE TEST THIS KITCHEN AND REPORT YOUR RESULTS
I thank chaimd for his bintonb0 tool, tadzio for his tools and Juggler for conv3 sourcecode.
I also thank Topogigi for his original procedure.
I modified conv3 tool to make it work with i780 rom files and made split and merge tools.
If you want to try this kitchen, I thank you!
[FONT="]If any guru in the forum wants to make a gui for this kitchen or insert tools for module, file and registry editing (like the ones you can find in other kitchens), it would be appreciated.[/FONT]
Issue 1: it seems there's a problem with Part02.raw conversion. It screws up connection settings. Problem is being investigated.
[Partial solution]: it seems that this problem is due to both size and language: I used an English rom to convert an Italian Part02.raw.
Using an Italian rom seems to solve the problem. But you must check the new rom size: if it's too big it gets cut down and it doesn't work.
Version 0.2: this version contains a new conv3 release. This release it's a little bit more complicated than the previous one but it supports a wider variety of rom images and guarantees correct conversions. Previous release could lead to incorrect roms so you should consider it as deprecated.
For Issue 1, limitations are still the same: you should use a rom of the same language of the dump and mind the result size
this is just great
great job
great effort for the great device.
I will try for sure, thanks a lot
Recreate???
At first thanks for the kitchen!!!
But I got one question... How can I rebuild the dump folder and what files are needed in the kitchen directory to recreate???
Do I just have to start RecreateBin.bat and it uses the files from the dump-directory???
THANKS!!
mievalt said:
At first thanks for the kitchen!!!
But I got one question... How can I rebuild the dump folder and what files are needed in the kitchen directory to recreate???
Do I just have to start RecreateBin.bat and it uses the files from the dump-directory???
THANKS!!
Click to expand...
Click to collapse
You must read the PDF file in the kitchen directory. Some parameters may change according to the ROME used
Hi Famusc,
Great Kitchen!
I have some questions before I can try your kitchen.
In the PDF you mentioned, an existing bin PDA ROM, what do you mean by that and how to get it? I have E1 ROM .raw files with me but not the .bin file.
Cheers,
Vibranze
vibranze said:
Hi Famusc,
Great Kitchen!
I have some questions before I can try your kitchen.
In the PDF you mentioned, an existing bin PDA ROM, what do you mean by that and how to get it? I have E1 ROM .raw files with me but not the .bin file.
Cheers,
Vibranze
Click to expand...
Click to collapse
you need flashable pda part file for convert,
like XHD1 pda file (you can find in this forum).
vibranze said:
Hi Famusc,
Great Kitchen!
I have some questions before I can try your kitchen.
In the PDF you mentioned, an existing bin PDA ROM, what do you mean by that and how to get it? I have E1 ROM .raw files with me but not the .bin file.
Cheers,
Vibranze
Click to expand...
Click to collapse
Hi,
Existing bin file will be used as a model ton convert your raw file. Famusc said that the bin file must be the largest possible. So far, we use the D1 bin file. The probleme is E1 raw file part is larger than D1 bin file.
There may also have concerns related to the language of ROM file. I try to cook a French raw file with an UK D1 rom, and the result is a broken ROM
Hi Eunjea & Webise,
Thanks for the explanation.
My current stock ROM is D1 and how to convert it to .bin format if I want to use mine?
Actually I always use English ROM and replace the wince.nls and add some fonts to support Chinese reading
Btw, how do I know what is the value for first jump, footer start and footer checksum address? In the PDF, the first jump address is on 444400 and in my bintonb0.txt I also have 444400, can I follow the same address?
Cheers,
Vibranze
webise said:
Hi,
Existing bin file will be used as a model ton convert your raw file. Famusc said that the bin file must be the largest possible. So far, we use the D1 bin file. The probleme is E1 raw file part is larger than D1 bin file.
There may also have concerns related to the language of ROM file. I try to cook a French raw file with an UK D1 rom, and the result is a broken ROM
Click to expand...
Click to collapse
I just want to backup my ROM which is built by my operator so that if I have problems with the upgrade I can always go back to my original ROM.
How can I create the bin files for te part 1 and 3?
Can anyone advise, as there is no bin file for the Omnia this kitchen will not be compatible, right? Or is there a way to create one?
I managed to dump an Dutch rom, version E1.. Could you explain how I can make a flashable image for the complete rom and/or how to make a radio rom from the three parts I dumped?
Furthermore, i have had some issues when I dumped the rom with the instructions that were in the readme.pdf.
There are some connection problems, that the originally phone doesnt have..when I flashed my rom, there werent any connection settings visible. e.g. settings > connections > connections > advanced > select networks, here was nothing visible.
It seems a bit like the same problem that people had with the english dumped E1 rom. Is there a chance that certain files from the raw files werent correctly put in the i780_flashable.bin (final product) ?
Is this the latest version of famusc's kitchen?