Database Users

Scoter Kitchen Release

The Scoter Kitchen team is proud to release the first release of the kitchen. This kitchen incorporates all the tools used by Oki and the rest of the team to decode, modify, and rebuild ROMs. It includes a help system that is meant to be clear to new users, and useful to old pros. Of course, this is only the first release, and thus will have bugs, and areas in need of improvement. This Kitchen is based on Bepe's WM5 Kitchen, and many of his tools. Special thanks to Mamiach, itsme, machinagod, gmap, buzzlightyear, and many others. Oki started the initiative, and we in the team are grateful for allowing us the privilege of contributing. There are also many additional tools not directly used for general ROM analyzing that can be found throughout. The kitchen is designed to be sleek and clear for the new user, while still containing all relevant tools for every part of the build process. This post is one of many across multiple forums. We are opening up development to all, and ask for volunteer translators. We will coordinate through forums primarily, but later plan on PM's, e-mail, etc. to effectively coordinate further development of the Scoter Kitchen. In addition, the kitchen is designed to extract most HTC ROMs, but it has it's limitations in the tools included, and the outlined process which are in the help files. Again, this will become better implemented through the help of the community. Now though this Kitchen is designed primarily for the Scoter, we intend to make this kitchen the primary hub for all PDA customization across all WM5 platforms. This post will be posted on many forums, and since the team members communicate primarily w/ English, we ask that those respond to this thread in English, or at least include an English translation. As a last note, you are solely responsible for any damage to your device or computer that might result from the use of the Scoter Kitchen, or any of it's parts. The following posts are left blank and will be filled w/ info later. Here are the download links:
http://www.MegaShare.com/107480
http://rapidshare.com/files/15460590/Scoter_Kitchen_1.0.exe.html
Regards,
Jason

Kitchen Team Members
Oki
JKR
DwD
Theo - Greek translation
Nadavi
gerttom
Preaper
Friends of the kitchen
Bepe (done as much as any other member and is considered an incredible contributor, and even that doesn't give him enough credit)
Kinger
blueboy
Marshal
cyril - French translation
bakker_be - Dutch and German translation
kterz
Regards,
Jason

Reserved,
Regards,
Jason

Bakup Files Of 0 Bytes
i had done a backup with ur utilites but the size of BDK0,BDK1 & BDTL0 is 0 byte why it is so ?????????? I stop here and wating for reply

to bad these dont work for the hermes .nb and .nbh files.. hopefully in the future it can be integrated..

shogunmark said:
to bad these dont work for the hermes .nb and .nbh files.. hopefully in the future it can be integrated..
Click to expand...
Click to collapse
Yep, we plan to add the nbhextract to the tools. And as far as the backup utility, that only works for the Scoter. We don't own htc devices, so that why we've asked the community to fill in the gaps. The extraction is universal, since there will be back and forth on various ROMs. The ROM installer also only works for the scoter. So, some info on these and anything else that the HTC community would like added, just tell us how. We can't really test these things, so we rely on you guys. At some point, the installer will ask what device you have, and install apps that apply to your individual devices.
Regards,
Jason

thats cool.. integrating the the hermes stuff will be difficult at this time anyway since we dont have a good set process on everything, we are still fighting the possibility of bad nand blocks with some cooked roms.. Something that i think would be really cool would be a full blown GUI with all these features built in..

here's some release notes I posted over at Buzz's site
JKR said:
4d45h said:
Questions.....
1. What is OS.bat. It says missing OS.bat when I click Cooker and start the build OS.
2. Where do you put pakages inside LOC(Bepe ways of cooking)
3. What is CEImage.bin? Is it the same as nk.nba base ROM Bepe ways.
Thanks and what a great tool.
Click to expand...
Click to collapse
1. That is a file created when you decode a ROM. I'm not sure what exactly it is for, bepe could answer that.
2. You can't use the current Kitchen ROM archives. The Scoter Kitchen incororates some more advanced versions of bepe's apps. The best way to describe the current situation is that bepe's WM5 Kitchen is version 1.0, and the Scoter Kitchen is 2.0. Since bepe was a big part of the Scoter Kitchen development, this should make sense. Keep in mind that this is not ready to be a replacement to bepe's kitchen yet, because it is only setup for building ROMs for the Scoter. We released it to all for many reason: 1) To speed up the development of the Kitchen for use w/ other devices, 2) it currently seems to be the most complete set of tools and help files for decoding ROMs, 3) the help files have a lot of info that may be interesting to many users. Most notable tools from bepe that are in the Scoter Kitchen are: DMP2PKG.exe, and PKG2DMP.exe. These tools actually have their own UI's that are fairly impressive. So to answer you question, you'd need to decode your current ROM and then begin modify that. Oki is the ROM hacker on the team. Essentially what he does, is extract the drivers (in the OEM folder) from various ROMs for our device, picks the best ones, adds in the SYS files and then puts in the packages for various apps. Anyways, bepe combined the LOC and SYS folders together into the SYS folder. for aesthetic reasons, the SYS folder is referred to as the OS folder in the build room. This is only a short cut name, and actual folder is still called SYS and is located in the Utilities folder.
3. Yes, this is in the help files in file:///C:/Scoter%20Kitchen/Utilities/Tools/Excess%20stuff/J-Guide/Extraction%20Room.htm?zoom_highlight=.bin .nb, .bin, and .nba are handled in the same way. just copy the location i posted into your browser address box.
Regards,
Jason
Click to expand...
Click to collapse
JKR said:
A few release notes. The install directory is C:\Scoter Kitchen. You will also see an uninstall script in c:\. This obviously uninstalls the Kitchen, everything is removed (including any work files in the kitchen) except the desktop shortcut. Also, since the imgfs tools are used so much by ROM cookers including myself, the Kitchen will place a copy of the imgfs tools in the %SystemRoot%\system32\ directory. This allows these tools to be opened by any command box w/o having to change directories. As you explore the kitchen you will see readme files in almost all folders, describing what is in that particular folder. Lastly, you will see like 15 command box shortcuts throughout the kitchen, this just makes things easier since their working DIR is the one they are placed in.
Regards,
Jason
Click to expand...
Click to collapse

Nobody here seems to be too forthcoming w/ info about other devices. Now I could go and search for all this info on my own, but then I probably wouldn't have the time or energy to modify the kitchen accordingly. W/ that said, I'll list some specific questions.
1. What programs are required for installing ROMs on various devices, and what are the procedures?
2. Are other devices capable of changing just the CE image through the boot loader, or does this have to be done using itsme tools? And what is the procedure?
3. Is the page pool setting in the same address on all HTC ROMs, or does this vary from model to model?
4. Explain the whole IPL and radio rom issue.
5. What would you like added to this kitchen?
You could just point me to specific posts too. Like I said, the Kitchen is completely functional for us Scoter guy's, so we won't spend the hours and hours required to research this stuff, since we won't get any benefit. But if some direction is given, we are willing, and wanting to expand our kitchen for use w/ other devices.
Regards,
Jason

I thought that it is just for Mio, and a little more documentation to it will be nice, thanks

xplode said:
I thought that it is just for Mio, and a little more documentation to it will be nice, thanks
Click to expand...
Click to collapse
Well it is fully functional for the Mio, but most all tools are here on this site. The two things specific to the Mio are the ROM backup utility, and the ROM update utility. Everything else applies to the HTC community. We are hoping that somebody will point us in the right direction for the equivalents of the two previously mentioned tools. Now as far as the documentation, yes, we plan to expand it. However, what specifically do you feel should be added?
Regards,
Jason

First of all, this's a very FANTASTIC tool!
In the BEPE's ROM Kitchen, there's an initflashfiles.txt file in the folder of each OEM apps which is used to create shotcut or copy/move files, its content will be combined with others into the initflashfiles.dat. Does this file still make sense in your kitchen?

BrightMoonHeart said:
First of all, this's a very FANTASTIC tool!
In the BEPE's ROM Kitchen, there's an initflashfiles.txt file in the folder of each OEM apps which is used to create shotcut or copy/move files, its content will be combined with others into the initflashfiles.dat. Does this file still make sense in your kitchen?
Click to expand...
Click to collapse
yep
Regards,
Jason

@JKR
I have reach up to using the DMP2PKG.exe stage, which can see the files in the *.dsm (see attached pic).
How to extract the files in the *.dsm?
How do I use RECMOD.exe?

CWKJ said:
@JKR
I have reach up to using the DMP2PKG.exe stage, which can see the files in the *.dsm (see attached pic).
How to extract the files in the *.dsm?
How do I use RECMOD.exe?
Click to expand...
Click to collapse
Hi,
You probably read the help files, huh? Yeah, those are dated, my bad. You don't actually have to touch DMP2PKG. The extract modules/files has dmp2pkg already scripted. At the time I wrote the help file, bepe didn't allow for command line commands. He has since, and I have scripted for it since. The following is an excerpt that I post over at Buzz's site.
JKR said:
Ahhh, I see problem. the .dat file needs to be in one of the folders, the OEM one i think. When Oki (rom team member) creates a file set, he includes the .dat file in the same folder that mxip_lang.vol is in, on our device it's 6acba9af-b4de-c7a3-802b-91ff1f140caf, but is probably different on yours. Anyways, I'm not sure where you got the idea to drag those to the tools folder, if it's in the help file, please tell me where. I've just re-looked at the help files, and they are quite dated. I've added a lot of automation to the process. Sorry for that. The correct procedure to extract a rom and rebuild it is to extract a .bin, .nba, .nb, or .nb0 file from your rom image. Then drag it to the extract modules. Open in another window the build room. put the .dat file (if it was placed in the modules folder) in the OEM folder. Drag all the contents of the OEM folder to the OEM shortcut in the build room. Drag all the contents of the SYS folder to the OS shortcut. Place the .bin or equivalent file in the rom template folder, and place the boot.rgu file in the \rom template\xip folder. The boot.rgu may be different for different devices, so use one that works on your device. I don't remember where exactly we got ours from, but I think it may have been from bepe's file set for his kitchen. Now launch the cooker. In the end, you should have a .bin file in c:\Scoter kitchen, aka one level up from the build room. hmmm, looks complicated. This is in the help files, but like I said, I need to update them, we were anxious to release the kitchen, since it had been under development for so long.
Regards,
Jason
Click to expand...
Click to collapse
As one more note, you probably wouldn't have to worry about the missing entries in the dmp2pkg interface. Probably just dated references from your ROM, it's a custom ROM?
Regards,
Jason

The rom is custom rom by Helmi, AKU3.5 v1.3, see my signature.
I will take sometime to digest you writings.
Still have not able to extract the *.dll, *.exe, *.hv, etc.
Will try adding & delete files later.

@JLR
I am back, manage to get some time to try the extract problem I faced.
Thanks, the extract works.
See the attached zip file of extracted files' directory list.
I have some questions,
1. what "<DIR> SYS" does, seems to have some *.dsm and some repeated DLLs.
2. If I do not need some *.exe, *.lnk, *.etc files, I just delete them?
3. How do I know that I fully deleted the files related to the feature that I do not want?
4. How do I know which corresponding *.dsm to be deleted?
5. How do I know which files goes to which directory in the \Windows\ of PPC?
6. How do I add files, how do I know what *.dsm to add and the name of the directories with very long string.

Questions please...
What is the importance of extracting files compared to extracting modules?
I have a base nbf file that I converted to nba file, that I want to modify to add the apps to build the ROM, I am confused as to which one I need, is it the files or the modules?

Great work! Thx for very useful tools!
What about map.txt support that helps to replace the GUIDs with the actual Package Names? I seen it in Bepe's kitchen...

JKR said:
Reserved,
Regards,
Jason
Click to expand...
Click to collapse
I need help. I was able to run the cooker file without any errors. Now what?
How can I recreate the .nbf file? Where can I find it? Should I be looking at the DUMP folder?

[APP] ReCOOKstruct - "all pkg in one" cooked ROM reconstructor

Hi!
This tool tries reconstruct cooked ROMs, that have been cooked using the "all packages in one" feature. It does this using a scaffold ROM, that should be as identical to the cooked one as possible for maximum recookstruction.
How does it work?
In theory
It loads the filenames and registry entries from the mock-up ROM and from the dumped ROM (using rgucomp to get the registry informations), then it tries to set up the same file and registry structure that the scaffold ROM had, but with the files and registry entries from the dumped ROM.
In practice
Copy the "oem", "sys" and "packages" directory from a non-cooked ROM in a directory. This will be the scaffold. The more identical this is to the cooked ROM the better. You can of course use a kitchenized official ROM too.
Next extract the contents of the cooked ROM. (using imgfstodump or something similar). Put the contents of the ROM in a "dump" directory besides the "oem", "sys" and "packages" directory.
Delete the dsm file from the dump, you won't need it. If it has an rgu file, delete it too.
Next copy reCOOKstruct into this directory, and run it (you should do it in a console, so you can see what it is doing). After a while it should create an "_output" directory, with the "oem", "sys" and "packages" directories recookstructed. All files and registry entries it couldn't handle using the scaffold will be put in the "Unknown packages" package in the "packages" directory.
Recooking
If you want to cook the recookstructed dump, then move everything from the "packages" directory to the "OEM" directory (they won't have an option.xml so buildos won't recognize them is they are there). Add ".ROM" and ".VM" to the "sys" directory from the dump (because they weren't copied). Next load up buildos, and cook. Be careful though! You will need the same (extracted) XIP in your kitchen as the dumped ROM had! Copying and porting XIP's in not in the scope of this topic...
Legal
If you recookstruct a ROM and use information from it to create your ROM, then add credit to the original author even if he didn't release his rom in kitchen form
Download
see attachments
EDIT: forgot to include rgucomp.exe, added

Awesome concept if it works. Ill give it a shot later when I get by a real computer thanks

hey sztupy great tool bro im gonna take a look at it (sector)!

thanks
will try tis ... really getting tired of the all in one package ... when wanna recook
kudos

rjmjr69 said:
Awesome concept if it works. Ill give it a shot later when I get by a real computer thanks
Click to expand...
Click to collapse
I've tried with two of my favorite ROM's (that have no kitchens) and it worked fine. Just don't forget to use the XIP/os.nb/"etc stuff not related to the imgfs section" from the cooked rom.

ugotta try this. thanks

Hi,
i have tested your tool, but comes error:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\BlackStoneKitchen>recookstruct
ReCOOKstruct
Cooked ROM reconstructor
by SztupY (http://winmo.sztupy.hu)
Reading data from dump
Reading dumped filelist
Reading registry hives
dumping dump/boot.hv
C:\DOKUME~1\alle\eee\eee.recookstruct.exe.2\app\recookstruct.rb:85:in ``': No su
ch file or directory - rgucomp -o "dump/boot.hv" -nologo (Errno::ENOENT)
from C:\DOKUME~1\alle\eee\eee.recookstruct.exe.2\app\recookstruct.rb:85
from C:\DOKUME~1\alle\eee\eee.recookstruct.exe.2\app\recookstruct.rb:83:
in `each'
from C:\DOKUME~1\alle\eee\eee.recookstruct.exe.2\app\recookstruct.rb:83
from C:\DOKUME~1\alle\eee\eee.recookstruct.exe.2\bootstrap.rb:77:in `loa
d'
from C:\DOKUME~1\alle\eee\eee.recookstruct.exe.2\bootstrap.rb:77
C:\BlackStoneKitchen>
Click to expand...
Click to collapse
C:\DOKUME~1\alle\eee\eee.recookstruct.exe.2\ what is it???
solution?
Folderstructure:
BlackStoneKitchen
-Dump
-OEM
-SYS
cheers

*_Touch_HD_* said:
Hi,
i have tested your tool, but comes error:
C:\DOKUME~1\alle\eee\eee.recookstruct.exe.2\ what is it???
solution?
Folderstructure:
BlackStoneKitchen
-Dump
-OEM
-SYS
cheers
Click to expand...
Click to collapse
it couldn't find rgucomp.exe. Did you copy that there too?
EDIT: I forgot to include rgucomp.exe in the zip. Redownload please.

nice, now works.
cheers

yes yes sztupy...
always re-inventing the wheel. Gonna use this methinks....
Thanks as always bro. Hope you keeping well!!

Ok so if I read this right what needs to happen is you have to find the DONOR rom which is most likely a stock or leaked rom and then the actual rom your want to depackage and follow the rest of the directions?
Can someone please verify this for me before I screw something up. Thanks
Would someone be willing to do a rom for me I think this is above my skills but I have a base rom I'm dieing to add too

rjmjr69 said:
Ok so if I read this right what needs to happen is you have to find the DONOR rom which is most likely a stock or leaked rom and then the actual rom your want to depackage and follow the rest of the directions?
Can someone please verify this for me before I screw something up. Thanks
Would someone be willing to do a rom for me I think this is above my skills but I have a base rom I'm dieing to add too
Click to expand...
Click to collapse
Yes, you're right. You'll need a donor that will be used as a pattern for the recookstruction. You can use anything ranging from official ROM's to kitchens with extracted ROM's

sztupy said:
Yes, you're right. You'll need a donor that will be used as a pattern for the recookstruction. You can use anything ranging from official ROM's to kitchens with extracted ROM's
Click to expand...
Click to collapse
Thank you sir for such a speedy reply. I've given it a shot but I dont know what the heck is going wrong I think its Vista even though I have full admin "hidden admin" user rights.
I'm going to have to fire up the xp machine see what happens there. But I would still love if someone could do it for me hehehe

rjmjr69 said:
Thank you sir for such a speedy reply. I've given it a shot but I dont know what the heck is going wrong I think its Vista even though I have full admin "hidden admin" user rights.
I'm going to have to fire up the xp machine see what happens there. But I would still love if someone could do it for me hehehe
Click to expand...
Click to collapse
vista shoudln't be a problem, I'm using Win7/vista miyself

Another fine thread added to my list of subscriptions ...
Cheers!

hilaireg said:
Another fine thread added to my list of subscriptions ...
Cheers!
Click to expand...
Click to collapse
This thread wouldn't be possible without your cooking tutorial
SztupY

can i reconstruct a rom that was made by another chef? if so how because i read everything and i am still clueless on what to do

Wooooooowwwwwwwwwww! Works great!! PROPS man!!
Oh wait, then it failed in SYS at sys/Redist_Lang_0409
Says: (** are username, disregard please)
C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:215:in `conv': "\343o Tom\351 and Pr\355n"... (Iconv::IllegalSequence)
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:215
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:214:in `open'
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:214
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:185:in `each'
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:185
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\bootstrap.rb:77:in `load'
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\bootstrap.rb:77
Any ideas??

Very much appreciated. I was in the process of developing the same exact thing. But you seem to have beat me to the punch. At least you made my job easier. lol

ookba said:
Wooooooowwwwwwwwwww! Works great!! PROPS man!!
Oh wait, then it failed in SYS at sys/Redist_Lang_0409
Says: (** are username, disregard please)
C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:215:in `conv': "\343o Tom\351 and Pr\355n"... (Iconv::IllegalSequence)
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:215
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:214:in `open'
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:214
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:185:in `each'
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:185
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\bootstrap.rb:77:in `load'
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\bootstrap.rb:77
Any ideas??
Click to expand...
Click to collapse
Iconv crashed because it expected an UTF-8 string but got something else. What locale are you in?

[GUIDE] Tg01 AUTO COOK&porting ROM kitchen with guid!fix bug!

I hope i can help u learn how to cook rom and makes it more easier!
1.Structure OF THE KITCHEN
ROOT OF THE KITCHEN-------
dump----> This will contan files dumped from ROM,like OFFICIAL ROMS.
OEM---->This folder contans all the OEM DRIVERS and OEM software
ROM\XIP\ ---->contain boot.rgu,don't mod or del it!
SYS -------->SYS of WM build
SYSNEW ------>TH SYS OF NEW version of WM building u will proting
temp ----->temp files,and ROM files u cooked are here
TOOLS --------->All tools that ness for cooking
XIPNEW ------>NEW XIP of WM version.there are two styles:XIP.BIN and MSXIPKernel.u can porting them by choose correct method in my bat command
reg&iniflashfiles_tools ------->Tools to edit reg files and initflashfiles.
HOW TO：
1、IF u don't want to Porting new version of wm and u just want to mod ,u can dump OFFICIAL rom.
TO DO：Place official ROM in root of kitchen，run "dump ROM.bat" and follow the instruction.when finished,u will find OEM AND SYS in DUMP\DUMP.Move them to root of the kitchen.and move xip.bin in dump to root of kitchen and rename it to xip_out.bin.Now,u can edit softwares in OEM and build as u like by run"Build ROM.bat"
2、IF u want to cook new version of WM build,just down load new SYS AND XIP file form somewhere like DFT.usually,u may only need these parts:COMM，COMM_0409,WVGA_COMM,WVGA_COMM_0409 and XIP.
UNZIP COMM，COMM_0409,WVGA_COMM,WVGA_COMM_0409 to SYSNEW folder,UNzip MSXIPKernel form XIP to XIPNEW folder then run"Build ROM.bat" and follow the guid.
sorry for my english...
hope u can understand...
-------------------------------------------------
sorry for my mistake..
i forget something important
just creat ROM\XIP\ folder in root of kitchen and put this boot.rgu in it
View attachment boot.rgu.zip
Download:TG01_ROM_KITCHEN.rar

ffboy2009 said:
I hope i can help u learn how to cook rom and makes it more easier!
1.Structure OF THE KITCHEN
ROOT OF THE KITCHEN-------
dump----> This will contan files dumped from ROM,like OFFICIAL ROMS.
OEM---->This folder contans all the OEM DRIVERS and OEM software
ROM\XIP\ ---->contain boot.rgu,don't mod or del it!
SYS -------->SYS of WM build
SYSNEW ------>TH SYS OF NEW version of WM building u will proting
temp ----->temp files,and ROM files u cooked are here
TOOLS --------->All tools that ness for cooking
XIPNEW ------>NEW XIP of WM version.there are two styles:XIP.BIN and MSXIPKernel.u can porting them by choose correct method in my bat command
reg&iniflashfiles_tools ------->Tools to edit reg files and initflashfiles.
HOW TO：
1、IF u don't want to Porting new version of wm and u just want to mod ,u can dump OFFICIAL rom.
TO DO：Place official ROM in root of kitchen，run "dump ROM.bat" and follow the instruction.when finished,u will find OEM AND SYS in DUMP\DUMP.Move them to root of the kitchen.and move xip.bin in dump to root of kitchen and rename it to xip_out.bin.Now,u can edit softwares in OEM and build as u like by run"Build ROM.bat"
2、IF u want to cook new version of WM build,just down load new SYS AND XIP file form somewhere like DFT.usually,u may only need these parts:COMM，COMM_0409,WVGA_COMM,WVGA_COMM_0409 and XIP.
UNZIP COMM，COMM_0409,WVGA_COMM,WVGA_COMM_0409 to SYSNEW folder,UNzip MSXIPKernel form XIP to XIPNEW folder then run"Build ROM.bat" and follow the guid.
sorry for my english...
hope u can understand...
Download:Uploading
Click to expand...
Click to collapse
U are the MAN!
Thank you.

Very nice
Hope I am now able to mod my favourite rom by myself now

Two worlds about how to integrate Sense in your ROMs maybe a good link if you have ?
Thanks
Edgar

I tested your tool and it is great as it is well guided.
but i can not find OEM folder in dump/dump only many folders containing "....dll" names and one folder called "SYS"
Also when editing OEM`s to the rom i get the error "Creating initialflashfiles.dat"
Looks like i am even not able to build a rom with a auto tool
P.S. Wanted to add cabs to your wm6.1 rom using this tool

eddgarms said:
Two worlds about how to integrate Sense in your ROMs maybe a good link if you have ?
Thanks
Edgar
Click to expand...
Click to collapse
Maybe this http://forum.xda-developers.com/showthread.php?t=633795 can help you.
FFboy: "IF u want to cook new version of WM build, just down load new SYS AND XIP file from somewhere like DFT."
What is DFT?

This is a DFT

Hello ffboy..
Can we use your tool to "modify" your sense rom, for exemple?
Thanks!
ps: moreover, i haven't got this folder "ROM\XIP\"...so i've got an error when i build the rom.
I tried to download your tool 3 times, but nothing....!!
What's wrong?
And I dumped the toshiba 6.5 rom, i did what you say in the first post and then i build the rom...
The original toshiba rom was 253mo and the new one is 244mo...but I didn't remove anything!!! Is this just because of the xip directory error i have during the "buildOs" process?
thanks!

iceeyes91 said:
I tested your tool and it is great as it is well guided.
but i can not find OEM folder in dump/dump only many folders containing "....dll" names and one folder called "SYS"
Also when editing OEM`s to the rom i get the error "Creating initialflashfiles.dat"
Looks like i am even not able to build a rom with a auto tool
P.S. Wanted to add cabs to your wm6.1 rom using this tool
Click to expand...
Click to collapse
Some roms that deleted all dsm and rgu files can't be dumped to OEM&SYS style
i can dump it out without do DM2PKG and copy all files in dump folder to SYS and do some mods.run kitchen maybe it works...
u want ro add cabs autoinstall on first boot?
just dump my rom to files and copy all off them into SYS,then creat a .rgu file and place it into a folder in OEM
add these in .rug file:
Code:
[HKEY_LOCAL_MACHINE\Software\TOSHIBA\AutocabInstall]
"cab1"=""
"cab2"=""
"Reboot"=dword:15

Nokser said:
This is a DFT
Click to expand...
Click to collapse
Yep!
That darkforcesteam。。。

pipolas said:
Hello ffboy..
Can we use your tool to "modify" your sense rom, for exemple?
Thanks!
ps: moreover, i haven't got this folder "ROM\XIP\"...so i've got an error when i build the rom.
I tried to download your tool 3 times, but nothing....!!
What's wrong?
And I dumped the toshiba 6.5 rom, i did what you say in the first post and then i build the rom...
The original toshiba rom was 253mo and the new one is 244mo...but I didn't remove anything!!! Is this just because of the xip directory error i have during the "buildOs" process?
thanks!
Click to expand...
Click to collapse
sorry fo my mistake...
download files in first threat
and it will fix erro..
the diff between ori rom and moded rom maybe because EXTRELOC useing a diff way to reloc moudules..i think

ffboy2009 said:
sorry fo my mistake...
download files in first threat
and it will fix erro..
the diff between ori rom and moded rom maybe because EXTRELOC useing a diff way to reloc moudules..i think
Click to expand...
Click to collapse
Thanks ffboy, i'll try!

pipolas said:
Hello ffboy..
Can we use your tool to "modify" your sense rom, for exemple?
Thanks!
ps: moreover, i haven't got this folder "ROM\XIP\"...so i've got an error when i build the rom.
I tried to download your tool 3 times, but nothing....!!
What's wrong?
And I dumped the toshiba 6.5 rom, i did what you say in the first post and then i build the rom...
The original toshiba rom was 253mo and the new one is 244mo...but I didn't remove anything!!! Is this just because of the xip directory error i have during the "buildOs" process?
thanks!
Click to expand...
Click to collapse
Size difference is mostly because of the IMGFS building, which may well be skipping free space at the end (used for ImageUpdate). It shouldn't matter too much.
I'll stick this, and unstick the other kitchen.

ffboy2009 said:
Some roms that deleted all dsm and rgu files can't be dumped to OEM&SYS style
i can dump it out without do DM2PKG and copy all files in dump folder to SYS and do some mods.run kitchen maybe it works...
u want ro add cabs autoinstall on first boot?
just dump my rom to files and copy all off them into SYS,then creat a .rgu file and place it into a folder in OEM
add these in .rug file:
Code:
[HKEY_LOCAL_MACHINE\Software\TOSHIBA\AutocabInstall]
"cab1"=""
"cab2"=""
"Reboot"=dword:15
Click to expand...
Click to collapse
Sorry i do not really get it
I dumped a official 6.5 Rom and there is like u said a OEM and a SYS Folder in dump/dump.
Using DMP2PKG i get an error on my win7 32bit by choosing "select folder"
Dumping your 6.1 rom it seems that in the dump/dump folder the OEM and his sub folders are not created, so all the data is loose.
will try some stuff and see where it gets me
Edit:
error : \.VM\imageinfo.bin not found, getting this with official and your 6.1

iceeyes91 said:
Dumping your 6.1 rom it seems that in the dump/dump folder the OEM and his sub folders are not created, so all the data is loose.
Click to expand...
Click to collapse
When dumping a cooked rom it is unlikley that you will get an OEM folder, i do not know why but the OEM parts can be found in the sys folder and relocated. Only dumping an original rom gives proper file segregation, ie OEM+SYS

Made my own rom now. Changed a official one and put some oem's in OEM folder.
Have some questions though:
How do you add the information to the rom , that it automatically adds a xxx.lnk file in startmenu for each program you have been put to OEM Folder??
Also how do you insert another input keyboard to the rom??
I wanted to add Neo2007 driverpack to my rom but it tells me that the xxx.dll already exists. how do i bypass this??
And how do I upgrade the netcf??
I now this is a lot of questions and maybe they are stupid, but i am totally new to rom-development. Thanks in advance
Thank you for this great tool

iceeyes91 said:
Made my own rom now. Changed a official one and put some oem's in OEM folder.
Have some questions though:
How do you add the information to the rom , that it automatically adds a xxx.lnk file in startmenu for each program you have been put to OEM Folder??
Also how do you insert another input keyboard to the rom??
I wanted to add Neo2007 driverpack to my rom but it tells me that the xxx.dll already exists. how do i bypass this??
And how do I upgrade the netcf??
I now this is a lot of questions and maybe they are stupid, but i am totally new to rom-development. Thanks in advance
Thank you for this great tool
Click to expand...
Click to collapse
Could you explain: if /OEM doent exit after DUMP, do you fill with your new cab (transform in OEM?) and add a registry entry ?

super_sonic said:
Could you explain: if /OEM doent exit after DUMP, do you fill with your new cab (transform in OEM?) and add a registry entry ?
Click to expand...
Click to collapse
I used this application to made my OEM's http://forum.xda-developers.com/showthread.php?t=525302
I just converted and put them into OEM folder.
Btw 1 thing concerning your 6.1 rom ffboy
Dumping it and putting everything to SYS does not work. I can not rebuild the rom , even if I do not add anything in OEM

iceeyes91 said:
Made my own rom now. Changed a official one and put some oem's in OEM folder.
Have some questions though:
How do you add the information to the rom , that it automatically adds a xxx.lnk file in startmenu for each program you have been put to OEM Folder??
Also how do you insert another input keyboard to the rom??
I wanted to add Neo2007 driverpack to my rom but it tells me that the xxx.dll already exists. how do i bypass this??
And how do I upgrade the netcf??
I now this is a lot of questions and maybe they are stupid, but i am totally new to rom-development. Thanks in advance
Thank you for this great tool
Click to expand...
Click to collapse
1.ALL files in SYS and OEM placed default in WINDOWS folder.check initflashfiles.dat in OEM_LANG_0409 and initflashfiles.txt in ur own oem folder.these files can change the place of file.
if u want add FFBOY.LNK to startmenu,add command like this.
Code:
Directory("\Windows\Start Menu"):-File("FFBOY.lnk","\Windows\FFBOY.lnk")
2.input keyboard can be added by download someone posted,u may search ur self.
3.if buildos tells u that XXX.DLL or some tile already exist,check the name and search in SYS or OEM to see if there exist a file in same name.
if exist,delete them except the newest one.
4.NETCF in wm6.5 already version 3.5

iceeyes91 said:
I used this application to made my OEM's http://forum.xda-developers.com/showthread.php?t=525302
I just converted and put them into OEM folder.
Btw 1 thing concerning your 6.1 rom ffboy
Dumping it and putting everything to SYS does not work. I can not rebuild the rom , even if I do not add anything in OEM
Click to expand...
Click to collapse
what buildos tell info to u?

[Q] [PROBLEM][HERMES-TYTN]Default.hv cooked ROM

Hi,
I have a really strange problem.
I have two HTC HERMES, one good that I use and a second that I use only fot test purposes because it's not in good conditions.
I cook ROMs with "ROMDonalds Kitchen" and I have neved had any problem.
Since yesterday, every new ROM I cook, I have this problem:
if I don't edit "default.hv" the cooked ROM goes well in both my HERMES, but if I edit it, the ROM can only be loaded on the second HERMES (the one not in good conditions).
In the other HERMES after flashing, when I make the reset or even the hard-reset, the ROM begins to boot but then stops after the first splash-screen and the screen becames white.
I always flash from SD (hermimg.nbh).
What can be the problem?
Can be a problem of the good HERMES of the two I have?
Can be a difference in hardware between the good HERMES, even if they are identical from outside?
Many thanks !

Hi,
I don't understand why you need to edit default.hv but probably you have your reason.
It's better to leave it untouched to my opinion.
To edit the registry you can edit the .rgu in the specific package or create
a new package with the new registry overwriting the first package registry.
The second suggestion you can keep your tweaks in every rom you cook and switch the stock packages more easy.
What you are writing is indeed weird but this way you avoid errors in the .hv files.
Edit; btw, because Hermes is a pretty old device I'm asuming the kitchen you use is still using .rgu instead of .reg in the packages, latest kitchens mostly use .reg
.rgu and .reg files are same and containing the registry.
Grtz,
Laurentius26

yeah its true, what do you change in the d.hv? maybe you can tell us, what about to use another kitchen? or do your changes in app.reg ext pkgs or in oem packages to void edit it

I edit .hv files when I add or remove programs from the ROM.
I've tried also Ervius kitchen but when I try to dump my ROMs It gives me some errors...the only kitchen I was able to use is RomDonald's..
Can You suggest me another good one?
Thanks

Airxtreme's Oskitchen or Barin's OSbuilder, they are both in Chef Central here.
You don't need to edit .hv files as when you remove the package all registry of that package will be gone too.
eryunt said:
I edit .hv files when I add or remove programs from the ROM.
I've tried also Ervius kitchen but when I try to dump my ROMs It gives me some errors...the only kitchen I was able to use is RomDonald's..
Can You suggest me another good one?
Thanks
Click to expand...
Click to collapse

I dont think ROMDonalds processes rgu files. If I remember correct, you have edit the hive files to use that kitchen.

Wow, that's gotta be a huge pain in the butt.

ai6908 said:
I dont think ROMDonalds processes rgu files. If I remember correct, you have edit the hive files to use that kitchen.
Click to expand...
Click to collapse
Yes, It is correct.
But the strange thing is that only one of the two Hermes I have, accepts the ROM after I edit the .hv files...
The question is:
Is there a separate memory where the hive is stored, and can this memory be faulty in one of my Hermes?

eryunt said:
...Is there a separate memory where the hive is stored, and can this memory be faulty in one of my Hermes?...
Click to expand...
Click to collapse
If you mean the fixed address - the answer is No. *.hv are files and files do not have the fixed address.

I've tried also Ervius Visual Kichen, but when I dump my ROM It gives me these two errors:
1- "Xipkernel's DSM not found! I'll create new...Maybe protected XIP (not portable !!!)"
2- "Boo.rgu in xip not found!Create new...But maybe ROM will be NON BOOTABLE !!!)"
What's wrong?
Thanks for all the answers You provide !
XDA, really a great Community !!!

Hi,
I don't know what you are doing to setup Ervius?
Are you importing a new stock rom into the kitchen?
The errors you can check:
Ervius kitchen/Rom/Shared/'Sys build'/MSXipkernel/
boot.rgu and the .dsm should be there.
Without boot.rgu and the dsm the rom won't boot.
Are all your desktop system files unhidden and vissible?
eryunt said:
I've tried also Ervius Visual Kichen, but when I dump my ROM It gives me these two errors:
1- "Xipkernel's DSM not found! I'll create new...Maybe protected XIP (not portable !!!)"
2- "Boo.rgu in xip not found!Create new...But maybe ROM will be NON BOOTABLE !!!)"
What's wrong?
Thanks for all the answers You provide !
XDA, really a great Community !!!
Click to expand...
Click to collapse

The visualization of hidden files is active in my PC, and I am trying to import a NON STOCK ROM to add or remove packages.
Ervius kithchen gives me the errors I described, and also OSKitchen gives me errors..
Can these kitchens import only STOCK ROMs?
I used ROMDonald's kitchen because It was able to edit a ROM that was already cooked...but the editing of .hv files is wrong...

I advise you to use a stock rom as you can test if everything is working ok.
After this you can do your modifications.
I know it's a bit of work but the advantage is to use a new kitchen which is much more configurable.
Editing .hv files isn't that good, but we talked about that already.
Another tip, I always zip my kitchen after I know a configuration is working and I flashed the rom succsesvol, before I continue to the next step.
eryunt said:
The visualization of hidden files is active in my PC, and I am trying to import a NON STOCK ROM to add or remove packages.
Ervius kithchen gives me the errors I described, and also OSKitchen gives me errors..
Can these kitchens import only STOCK ROMs?
I used ROMDonald's kitchen because It was able to edit a ROM that was already cooked...but the editing of .hv files is wrong...
Click to expand...
Click to collapse

eryunt said:
Yes, It is correct.
But the strange thing is that only one of the two Hermes I have, accepts the ROM after I edit the .hv files...
The question is:
Is there a separate memory where the hive is stored, and can this memory be faulty in one of my Hermes?
Click to expand...
Click to collapse
It doesnt make sense why one device would run it, and the other one dont! Are you sure the hive files do not have any errors?
Try to flash a stock ROM first, then flash the cooked one. I know hermes has ext storage, and that can through errors...

ai6908 said:
It doesnt make sense why one device would run it, and the other one dont! Are you sure the hive files do not have any errors?
Try to flash a stock ROM first, then flash the cooked one. I know hermes has ext storage, and that can through errors...
Click to expand...
Click to collapse
That's the point...It's a nonsense..
I've already tried to flash stock ROM on both devices before flashing the cooked ROM, but It's always the same nonsense, one loads the ROM, the other doesn't...
At this point only a malfunction or a difference in hardware between my two devices could explain this strange behaviour
Don't know how to solve...

are you trying to recook my roms? hahaha just kiddin
everybody knows that we don thave bootable and full dumped roms from customized ones, due to DSMsif you want to make a roms looks like or be something like a... i recommend to ask for the kitchen many retired chefs on Legacy devices can share it to you or just dump the rom and xtract the things you want
but make your own Stock OEM an set good your Native Kernel

Upgrading from 6.1 to 6.5

I have cooked a few roms for my diamond using the HTC WM6.1 1.93 release as a base. But i'd like to try Titanium and I gather i'd need WM6.5.
I have downloaded OEM xip kernel, SYS_23563_192DPI_0409, SYS_23563_Common and SYS_23563_XIP.
Please could someone give me some idea of what to do with these folders.... I use EVK 12.5.8

rikpotts said:
I have cooked a few roms for my diamond using the HTC WM6.1 1.93 release as a base. But i'd like to try Titanium and I gather i'd need WM6.5.
I have downloaded OEM xip kernel, SYS_23563_192DPI_0409, SYS_23563_Common and SYS_23563_XIP.
Please could someone give me some idea of what to do with these folders.... I use EVK 12.5.8
Click to expand...
Click to collapse
first thing is port the SYS (common and DPI 192),unpack this two archives then useing the Packer.jar you will create a new SYS for youre build,next you will need some OEMDrivers(the touch.dll for WM 6.5) and a OEMXIPKernel (the nk.exe for WM 6.5) and last but not least the MSXIPKernel,in ROM/Shared (just create a new folder and copy the content of SYS_23563_XIP.

Thankyou so much for your reply.
I have just built my first wm6.5 rom and will attempt to flash in a minute.
The only thing i'm left slightly confused about is a few bits in the OEM folder.
OEM/DIAMOND/COMMON/OEMVERSION/mxipupdate_OEMVERSION_100.provxml
It reads "ROMVersion" value="1.93.401.2"" Surely I should have a second file for wm6.5?
Also in ROM/DIAMOND there were a load of files in the OEMXIPKernel I downloaded that wanted to overwrite some existing files.... namely info.txt, ROMHdr.bin, xip.bin, os.nb.payload.
I didn't let them overwrite but do I need to keep both sets of files?

rikpotts said:
Thankyou so much for your reply.
I have just built my first wm6.5 rom and will attempt to flash in a minute.
The only thing i'm left slightly confused about is a few bits in the OEM folder.
OEM/DIAMOND/COMMON/OEMVERSION/mxipupdate_OEMVERSION_100.provxml
It reads "ROMVersion" value="1.93.401.2"" Surely I should have a second file for wm6.5?
Also in ROM/DIAMOND there were a load of files in the OEMXIPKernel I downloaded that wanted to overwrite some existing files.... namely info.txt, ROMHdr.bin, xip.bin, os.nb.payload.
I didn't let them overwrite but do I need to keep both sets of files?
Click to expand...
Click to collapse
the part with the rom version, you can modified as you wish ,yo can put you're name in there(PS: dont modify the phones ID or things like that)...then,you don't need the info.txt files anymore,delete them(PS: don't delete them if you are trying to build a new XIP.bin).If it says to overwrite.overwrite them with the new ones.Because the xip.bin,os.nb.payload,and the ROMHdr.bin are the old build files.so you need to replace them with the new ones,but you need to make a backup,just to be shure...or if you dont have the xip.bin and also the os.nb.payload for the new build you have to create the xip.bin with XIPport.exe and then we use again the XIPport app to inplant the new created xip.bin in the OS.nb.payload...that its a little tricky even i can do it properly