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?

[NEW RELEASE] ◄ HyperCore Kitchen ► MULTIDEVICE !!!

HyperCore
PUBLIC BETA​
The most complex KITCHEN a begginer cook may ever need.
Easy to use but also very complex, it can be usefull to anyone.
Why ask and wait for others to make the perfect ROM for you when you got the power to do it yourself ?
~. Base ROM .~​* NO BASE ROM ! but ANY ROM !
~. Best part .~​* IT USES TADZIO TOOLS
* YOU CAN OPTIMISE EXE's and DLL's, SO IF YOU WANT EVEN MORE SPACE, YOU'LL GET IT
* IT CAN BE USED ON ANY DEVICE WITH VERY LITTLE MODIFICATIONS !!!!!
* NO LONGER LIMITED BY ANYONE OR ANYTHING.
* YOU CAN COOK ANY ROM YOU LAY YOUR EYES ON VERY EASY
* IT HAS ADVANCED ERROR CHECK
~. It will install .~​Core folder on the system drive. Some tools and settings required.
HyperCore folder on the Desktop. There is your kitchen. You can move it wherever you want.
The place where you actually use it is HyperCore\Panel.
~. How To .~​- First of all edit the file named "Device.txt" located on the "Core\ACK\" folder located on systemdrive (mostly drive C:\)
Edit as following.
If you have a :
HTC Wizard : " set device=Wizard "
HTC Hermes : " set device=Hermes "
HTC Artemis : " set device=Artemis "
HTC Herald : " set device=Herald "
HTC Universal : " set device=Universal "
HTC Trinity : " set device=Trinity "
HTC Prophet : " set device=Prophet "
Click to expand...
Click to collapse
Save it and then you're good to go.
It's much similar to the old Core kitchen...so those of you who used it ...will feel comfortable with it. Regenerated batch scripts, better, and i hope bug free.
~. Guides .~​* Hermes Cookbook - THANKS to sambartle
* My Way of cooking
* How to ADD/REMOVE programs -THANKS to mfrazzz
~. Notes .~​Since this is still a public BETA, I await your problems/ideas/concepts.
If you spot a bug, i suggest to send me a PM as well as a post on the thread.
I suggest having a ROM to make a backup in case you do something wrong
I created and tested this tool for WindowsMobile 6 , but WM5 should work OK too.
~. Download .~​
RapidShare
Special thanks :
* Papamopps - for real support
* nandlal_mk - for answering questions and DSM editor
* mUn - for finding the time to answer some of my questions
* molski - for i started working on his tools and still used some of them
* Tadzio - for his tools and patience
* bepe - for his tools
* the-equinoxe - for his splash-screen tools
* naboleo - for his initflashfiles generator
* dutty - for his NBH Tool
few others that surely i forgot to mention Sorry..

A very very very big THANK YOU anichillus! Your hard work and contribution is appreciated.

Great works anichillus....!
Thanks a lot

Very nice! Can't wait for a custom rom

It seems really good

Good work man!! will give it a try, post back results later!

Tell me guys if anyone tried it and if any problems.
A feedback would be nice.

anichillus,
thanks for the great stuff. BTW, can you advise how i can repackage the OEM and SYS folder back to *.nb file.
Thanks...
anichillus said:
Tell me guys if anyone tried it and if any problems.
A feedback would be nice.
Click to expand...
Click to collapse

simontee said:
anichillus,
thanks for the great stuff. BTW, can you advise how i can repackage the OEM and SYS folder back to *.nb file.
Thanks...
Click to expand...
Click to collapse
Once you run the BuildOS program in Build menu, if you follow those stepps you'll have the OS.nb in the temp folder. After that, you will be asked if you want to convert it into Signed .nbh and it will be moved into the HTools in the Tools folder. Just follow the tutorial in Help folder, you will figure it out.
Cheers

It works !!!
anichillus,
thanks for the guide and it works for me. I have re-cooked BEPE WM6 WWE OS.nb and it works smoothly for me.
removed some files :-
- transcriber
- redundant ringing tone
- redundant pic and image file
- redundant help files
BEPE WM6 WWE
Storage In Use : 5.17 MB
Program In Use : 22.4 MB
and now my self-cooked ...
Storage In Use : 2.79 MB
Program In Use : 25.7 MB
Thanks again !!

simontee said:
anichillus,
thanks for the guide and it works for me. I have re-cooked BEPE WM6 WWE OS.nb and it works smoothly for me.
removed some files :-
- transcriber
- redundant ringing tone
- redundant pic and image file
- redundant help files
BEPE WM6 WWE
Storage In Use : 5.17 MB
Program In Use : 22.4 MB
and now my self-cooked ...
Storage In Use : 2.79 MB
Program In Use : 25.7 MB
Thanks again !!
Click to expand...
Click to collapse
can u tell me the steps of cooking?

I want translate BEBE WM6 WWE to French. But i don't know the method. I can extract mui files from emulator but next ? I misses files into emulator. Do you have a tutorial ?

can this tool be used to change to vendor / country id of a rom - ie change the official htc wm5 rom so that it may install from bootloader on a locked o2 orbit?
thanks.

chickyd said:
can this tool be used to change to vendor / country id of a rom - ie change the official htc wm5 rom so that it may install from bootloader on a locked o2 orbit?
thanks.
Click to expand...
Click to collapse
No! It can create nb/nba file to flash on a live devices. But created nbh files are invalid. So you cannot flash at Bootloader!

first time using kitchen stuck
I just have one question completely new to this stuff how do i take the missing files that are on the package tool and put the back to the sys folder that they need to be in sorry if question is stupid

Hi!
Thanks for an awesome toolkit!! I have some questions regarding home brew
1) Could I cook a ROM containing some of the applications I usually installs on my device, for instance tomtom, pocket plus, resco explorer and so on?
2) How do I change language on the ROM I cooks? I know I have to extract the resource from the emulator ROM's, but then...
3) Can I mix and match resources in different languages? I want a WWE ROM, but with the Norwegian onscreen keyboard?

Thanks for this good tutorial, I'm still trying to find out all options that there are. I'm looking forward to see a complete tutorial about all the functions, e.g. how do I integrate my own apps into the ROM or EXT Rom, signing files.....
My first ROM didn't work but I'd really build a ROM that increases my program memory as already mentioned and all my standard apps preinstalled, own splash screen,.... But that will take some time.
I translated the tutorial into German, send me a PM to tell me where to send it.

Web
Is there a problem with the website? I can ping it but I can't read it.

Thank you so much anichillus for your great posts and releases. I'm using your Kitchen, and I have nothing but all the good to say.
Though, i have a few questions. I understand that making the Rom by using the CreateROM.bat file makes it so much easier. But, I would like to know what exactly hapens when we execute CreateROM.bat.
why do we have many seprate folders like SYS, ROM, flashrom, Tools?
i know that we can use the OEM folder for adding packages.
i also know that the Tools folder has all the programs ndded to make the rom.
What is the SYS folder? what does it do?
What is the ROM folder? what does it do? Can we change the file Flash.nbo? if we can, how is the final ROM affected?
Thanks again for all your support.

majdi_alkurd: click right mouse button on createROM.bat, then Edit and you'll see what exactly does it do.

Rebuild *.dsm --- BuildDSM.exe

Hi, I dont know how Rom Kitchen Cooker were doing this till date ( some like me just ignored in past) but some how i got this (iv not created it) and would like to share this.
1) Place ur OEM, with its dsm file inside.
2)take out option.xml temporarily
3)Drag and drop OEM folder over BuildDSM.exe
4)u got ur dsm populated.
5)place back option.xml in OEM folder, and thats done.
View attachment BuildDSM.zip

BTW, I always leave my Option.xml in the OEM. Never had a problem

looks very nice does it work for system dsm's?

Midget_1990 said:
looks very nice does it work for system dsm's?
Click to expand...
Click to collapse
ya its working on sys dsm's also.

looks easy, i look forward to trying it, great work.

oww..!
nandlal_mk.Thanks a lot..!
Trying now..!

Thanks man !
I'll use it now.
I had hard time locating this one. Good thing you sent the link in the pm

To be honest I dont quite get what this does. I thought that for OEM packages we make, we just need a zero-bite file with the GUID and .dsm in the end.

WizeMan said:
To be honest I dont quite get what this does. I thought that for OEM packages we make, we just need a zero-bite file with the GUID and .dsm in the end.
Click to expand...
Click to collapse
Yes, but that would result with "missing" packages

Aha, Uhum, I Get it.
Is that really all the need and reason to use a populated DSM?
So that when the Rom gets extracted there won't be missing files?
So Empty Bites DSM have no effect on performance or whatsoever?
(Except the fact they or 0 bites)

I've got 2 small questions;
1. Can somebody explain to me what the function of these *.dsm files is?
2. Wouldn't it be nicer to exclude the option.xml file automatically instead of taking it out by hand?
But as far as I can understand it looks very promising!!!

Great tool, just trying it today, big thanks !!!
Is there an option to bypass the "press a key to continue" ?

looks easy, trying it, great work.
Thank you very much.

The system cannot execute the specified program.
Requires:
Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)
http://www.microsoft.com/downloads/...D9-AE1A-4A14-984D-389C36F85647&displaylang=en
... installing VC2K5 SP1 Redist allows the application to run although Dependency Walker also shows a delay-load on DWMAPI.DLL.

EasyPortOven V2.2 [Updated May 11 2008]

This is a release for my ROM porting kitchen. It ports both XIP's and SYS folders. It currently supports the following:
Herald
Wizard
Prophet
Kaiser
Elf/Elfin
Hermes
Zinc
Athena
http://www.darthnet40.com/xda/ivanmmj/Kitchens/
(You will need 7-Zip to open the file.)
This is compatible with Bepe's extended kitchen, but I don't believe he ever released one for every device out there. It requires a ROM folder with an extracted XIP folder within it. Just download the Herald's and you'll see what I mean. The ONLY tested section has been the Herald section as that's the only device that I have.
If your device is compatible with Bepe's kitchen or my kitchen, it will automatically launch the kitchen right after.
Instructions:
Delete your old SYS folder
Place the SYS file you wish to port into Working_Folder
Place your xip.bin that you wish to port into the Prepare folder
*Note: Close the XIPPort program after pressing "Make Packages." The script will take over after that.
You should not have a Working_Folder with an OEM, SYS and XIP folder (and a Tools folder if you have Bepe's kitchen, even more if you have my kitchen.)
Double click on the RunMe file and choose your device.
For those who have a kitchen:
Place bepe's kitchen in the Working_Folder (so that OEM/SYS/ROM and other folders are right within Working_Folder.) Alternatively, you can place also place all the files into EasyBakeOven's folder. Allow the Working_Folder to override EasyBakeOven's Working_Folder. You will not loose any data but will bypass a few "info" scripts. This will not cause any problems.
Obligatory Warning Label:
Use this at your own RISK. I cannot be held liable for any damage caused to your device by your own mistakes or by my mistakes in the instructions.
If you wish to know how to do this manually, head over to my HowTo thread.
Thank you's go to:
Bepe for his Extended kitchen and Herald/Atlas files
ababrekar for the elfin files
l3v5y and xvx45 for the Prophet files
character and ginminded for the Wizard files
Script for the Kaiser files
tjkhattak61 for the Atom Exec files
cruzzmz for the Zinc files
caxio for the Hermes files
irus for the Athena files
Changelog
V2.2
Added Athena Compatibility
V2.1
Added Prophet Compatibility
Added Elfin/Elf Compatibility
Added Hermes Compatibility
Added Kaiser Compatibility
Added Zinc Compatibility
Added Atom Compatibility
V2
Added Wizard Compatibility
Rewrote script to add expandability
V1.5
XIP porting complete
V1
SYS porting complete

Woo! I've failed to find a link for this up till now, but now I can cook some new ROMS!!
One thing, the read me doesn't include some of the more reason compatibility improvements...
Welcome to EasyBakeOven!
Devices supported:
Herald/Atlas
Wizard
Note: Make sure that the XIP in your recieving folder has been extracted already (You should have a ROM folder with a XIP folder inside it.) This is not an issue if you're using Bepe's Extended 6.1 kitchen or my own JustClean EasyBakeOven.
Thank you's go to:
Bepe for his Extended kitchen and Herald/Atlas files
ababrekar for the elfin files
l3v5y and xvx45 for the Prophet files
character and ginminded for the Wizard files
Script for the Kaiser files
tjkhattak61 for the Atom Exec files
cruzzmz for the Zinc files
caxio for the Hermes files
irus for the Athena files
Click to expand...
Click to collapse

l3v5y said:
Woo! I've failed to find a link for this up till now, but now I can cook some new ROMS!!
One thing, the read me doesn't include some of the more reason compatibility improvements...
Click to expand...
Click to collapse
Noted. Thank you!

Has anyone found this even remotely useful? If not, I will not pursue adding more devices.

Has anyone found this even remotely useful? If not, I will not pursue adding more devices.
Click to expand...
Click to collapse
I have! I've ported a Kaiser XIP and a Touch one to the Prophet! Problem is I couldn't find the latest builds so they where slightly out of date...

l3v5y said:
I have! I've ported a Kaiser XIP and a Touch one to the Prophet! Problem is I couldn't find the latest builds so they where slightly out of date...
Click to expand...
Click to collapse
Just for being nice to me, here you go!
That's the newest official build. Be careful of anything "newer," they're fakes.
It's the one labeled 19213.7z
You'll need 7Zip to open the file. In it as the xip.bin and the SYS folders.

Yay!!!
Porting time!

I have one feature request!
Would it be possible to build a feature in that cleans out the folders before porting?

I think I'll test later cause actually I'm in exam but I think it work, I'm on the same device as l3v5y so I'll make my test and maybe take to you Artemis files (my other phone)
Thank for your hard work

Great tool ivanmmj.... I have a few questions. I guess I don't fully understand the process.
I've been able to get the XIP folder, os.nb.payload and romhdr.bin files from a KAISER rom... plus I used the .VM and WinCENLS_WWE folders from a working HERMES rom, but I can't seem to get past the second boot screen. A question I had is... do we use the os.nb.payload and romhdr.bin we got from the KAISER? or do we use those from a working hermes rom? and the XIP directory, do we need to change anything in there? or is just extracting it out, enough to work?
Thanks in advance.

Awesome tool, looks like a dummy can me even port ROM's will try it out sometime. Thanks bunches!

l3v5y said:
I have one feature request!
Would it be possible to build a feature in that cleans out the folders before porting?
Click to expand...
Click to collapse
Already ahead of you. Today I noticed that I tend to leave a mess behind. lol I'll have it remove the files before replacing them, then I'll have it delete the extra files created during the process when it's done. (This part is already ready but I just haven't uploaded it. The removing the files before replacing them, I haven't done so, yet. Although this might not really be needed. Only the cleaning after part.)
...Maybe I don't know what you're talking about. lol
Explain it to me.

AssassinsLament said:
Great tool ivanmmj.... I have a few questions. I guess I don't fully understand the process.
I've been able to get the XIP folder, os.nb.payload and romhdr.bin files from a KAISER rom... plus I used the .VM and WinCENLS_WWE folders from a working HERMES rom, but I can't seem to get past the second boot screen. A question I had is... do we use the os.nb.payload and romhdr.bin we got from the KAISER? or do we use those from a working hermes rom? and the XIP directory, do we need to change anything in there? or is just extracting it out, enough to work?
Thanks in advance.
Click to expand...
Click to collapse
You need the XIP folder, os.nb.payload and romhdr.bin of YOUR device and the xip.bin and SYS folder of the rom you want to port INTO your device. Which device do you have? Tell me and I'll "draw" a map of what goes where.

xvx45 said:
I think I'll test later cause actually I'm in exam but I think it work, I'm on the same device as l3v5y so I'll make my test and maybe take to you Artemis files (my other phone)
Thank for your hard work
Click to expand...
Click to collapse
That would be more than welcomed especially since I'm gonna use my Herald cooking class and modify it to teach Artemis users, also.
ai6908 said:
Awesome tool, looks like a dummy can me even port ROM's will try it out sometime. Thanks bunches!
Click to expand...
Click to collapse
My hope is that it will allow just about anyone to port a ROM. ^_^

ivanmmj said:
You need the XIP folder, os.nb.payload and romhdr.bin of YOUR device and the xip.bin and SYS folder of the rom you want to port INTO your device. Which device do you have? Tell me and I'll "draw" a map of what goes where.
Click to expand...
Click to collapse
Thanks for replying ivanmmj... I have a hermes, and I've been doing exactly that... my problem is when I go to build it, I get "An unhandled win32 exception occurred in buildxip.exe [2276]"
If I put in my older XIP build, buildxip works fine... so I'm lost now. Oh, and I'm trying to port the 19213 official att kaiser rom XIP.

AssassinsLament said:
Thanks for replying ivanmmj... I have a hermes, and I've been doing exactly that... my problem is when I go to build it, I get "An unhandled win32 exception occurred in buildxip.exe [2276]"
If I put in my older XIP build, buildxip works fine... so I'm lost now. Oh, and I'm trying to port the 19213 official att kaiser rom XIP.
Click to expand...
Click to collapse
You'll need:
OEM: hermes
ROM folder: Hermes (uncluding the XIP folder and all the other files)
SYS folder from kaiser (look for and remove MSkernel from this folder... I'm not 100% on that folder yet and future versions may handle that folder automatically)
Place the xip.bin from the kaiser into the prepare folder.
Now run the RunMe

ivanmmj said:
You'll need:
OEM: hermes
ROM folder: Hermes (uncluding the XIP folder and all the other files)
SYS folder from kaiser (look for and remove MSkernel from this folder... I'm not 100% on that folder yet and future versions may handle that folder automatically)
Place the xip.bin from the kaiser into the prepare folder.
Now run the RunMe
Click to expand...
Click to collapse
I really appreciate your help ivanmmj, same thing again. It chokes up on BuildXIP.exe ...I have BuildXIP version 0.53 if that makes any difference. I tried with two XIP versions... 19209 and 19900. I'm about to give up.
Oh and I have Visual Studio 2008 installed, so I don't think it would be the runtimes... would it?

AssassinsLament said:
I really appreciate your help ivanmmj, same thing again. It chokes up on BuildXIP.exe ...I have BuildXIP version 0.53 if that makes any difference. I tried with two XIP versions... 19209 and 19900. I'm about to give up.
Oh and I have Visual Studio 2008 installed, so I don't think it would be the runtimes... would it?
Click to expand...
Click to collapse
It might be.... I'll have to do some research...

Ok, I even installed the vs2008 runtimes, same thing.. I found buildxip v.54, same thing... then i moved the whole ROM folder (new XIP) out and put in the old 19209 one and it ran... so maybe there's something wrong with 19213 with hermes? ok, I give up. Thanks for your help!!

19213 porting to elfin
i'm trying to port the 19213 to my elfin, and after porting when i use bepe's kitchen, it gets stuck at this screenshot. anybody help!!!

Can ervius Visual Kitchen be used with Extreloc?

I'm trying to get an "old-style" 6.5 ROM built using EVK, and while using wmreloc builds the ROM successfully, it never boots. I've read about Extreloc in a few places, and apparently it's supposed to a better job of relocating modules. So does anyone know how to integrate Extreloc into EVK to cook a bootable, dumpable (possibly even Image Update-Ready) ROM?

Bepe specifically designed platformrebuilder to delete dsm files and the final s00x file in modules more or less to save space (he compared it to removing the ULDR in XIP) and improve module loading speed so unless you can make prb NOT do that then I doubt it. Although it sounds really interesting, I too wish we could try another reloc.

Psyki said:
Bepe specifically designed platformrebuilder to delete dsm files and the final s00x file in modules more or less to save space (he compared it to removing the ULDR in XIP) and improve module loading speed so unless you can make prb NOT do that then I doubt it. Although it sounds really interesting, I too wish we could try another reloc.
Click to expand...
Click to collapse
But I think the "old-style" option in Visual Kitchen actually adds the DSMs back in (or re-creates them) - have you tried it?

Extreloc
Speaking of Extreloc - does anyone know where I can find it (along with, perhaps, some instructions on the parameters to use with it)?

Captain_Throwback said:
Speaking of Extreloc - does anyone know where I can find it (along with, perhaps, some instructions on the parameters to use with it)?
Click to expand...
Click to collapse
Here are some links but not in English!!!
http://4pda.ru/forum/index.php?showtopic=137276
http://3ppc.net/forum/showpost.php?p=282398&postcount=45
Good luck!

kokotas said:
Here are some links but not in English!!!
http://4pda.ru/forum/index.php?showtopic=137276
http://3ppc.net/forum/showpost.php?p=282398&postcount=45
Good luck!
Click to expand...
Click to collapse
Thanks for these links!!
I did find a downloadable Extreloc, and the one link had a good manual (thanks to Google Translate). Of course, I still can't cook an old style ROM with EVK, because, even though the OEM & SYS work okay, DSM Editor doesn't have the information to create DSMs for the EXT packages, apparently, which is where the issue lies. I wonder if I can create DSMs for all of the EXT packages, put them in the packages, and see if I can dump the ROM?

Captain_Throwback said:
Thanks for these links!!
I did find a downloadable Extreloc, and the one link had a good manual (thanks to Google Translate). Of course, I still can't cook an old style ROM with EVK, because, even though the OEM & SYS work okay, DSM Editor doesn't have the information to create DSMs for the EXT packages, apparently, which is where the issue lies. I wonder if I can create DSMs for all of the EXT packages, put them in the packages, and see if I can dump the ROM?
Click to expand...
Click to collapse
i havent tried cooking old style rom in a long time, but doesnt evk place dsm/rgu in ext pkgs when you dump a stock rom? thats one reason i stopped using evk to dump stock roms and rebuild, now i use extrebuild its so much cleaner

twopumpchump said:
i havent tried cooking old style rom in a long time, but doesnt evk place dsm/rgu in ext pkgs when you dump a stock rom? thats one reason i stopped using evk to dump stock roms and rebuild, now i use extrebuild its so much cleaner
Click to expand...
Click to collapse
It puts them in the folder with the EXT packages, yes, but not in a place where they get cooked into the ROM (if cooking a new-style ROM, that is). It also creates a package.ini file that details the dependency information for each package, based on the info in the DSM. It only keeps them there for cooking an "old-style" ROM, which is what would make this work as I would like it; except it doesn't work properly, and for user-made packages that don't include DSMs, DSM Editor doesn't seem to create them properly when cooking an old style ROM.

i cooked an image update rom for kaiser back last year, and i just used build OS old style kitchen to cook the rom and it worked i cant wait to be able to start using image updater, but its a real pita to cook a rom that it will work on now...and like you said its really hard to put in custom pkgs, with kaiser i basically re-cooked a stripped down stock rom. Da_G is getting closer to having his new kitchen tools done, then we should be able to build roms easily that will work with the updater

@captain
I am also looking for the exactly the same. I too want to cook in old style. But, not able to find any rebasing tool equivalent of the one in platformrebuilder.exe. Extreloc, though, is claimed to work well but for me it does not give very dependable results.
I am also interested in this kind of solution Pl update us here in case you manage to find any...

Maybe this helps?
I don't know where I have it from anymore, if I remember good it was Conflipper who shared that maybe at Mobile Underground , haha I'm realy not sure.
LoL
But I think it's something you can use.

Laurentius26 said:
Maybe this helps?
I don't know where I have it from anymore, if I remember good it was Conflipper who shared that maybe at Mobile Underground , haha I'm realy not sure.
LoL
But I think it's something you can use.
Click to expand...
Click to collapse
Thanks Leo, but EVK comes with this version of WMReloc. I've tried using it to cook a 6.5 "old-style" ROM, and while the ROM compiles successfully, it won't boot. I'm thinking it could be related to module overlaps due to WMReloc's not handling the 6.5 modules properly (even though I know it's supposed to). In fact that may not be the case, but I thought EXTReloc was supposed to a better job of this. I think the real issue (and I may have already stated this) is that the DSMs from the EXT packages aren't being properly re-created during the build process by DSM Editor (perhaps that's outside the realm of what it can do?). In most cases, my EXT packages have been dumped from official ROMs, and as such have the DSM/RGU's outside of the "files" folder. They should be easily re-integrated during cooking, but I don't think that step is taking place. Perhaps it's as simple as adding a command into the batch file to copy those files into the "dump" folder for each package (I'm not really sure the best way to do that, though)? And what about packages that happen to be missing that information? Is there a way to re-create those on the fly, or would that need to be done manually? I assume for custom packages (like graphics, etc.), dependency information isn't really needed, but when dumping the ROM, those files won't have a home, I suppose .

Here's a quote from Da_G, maybe you need to use Misar's G'Reloc?
Btw I'm just a nOOb with all these tools and batch files, I know a little but just trying to help you.
Maybe a little about batches... and I read a lot.
Da_G said:
WinMo 6.5 improves on this by opening up Slots 60 and 61 to Modules - yielding an extra 64mb of potential Virtual Memory space. (the allocation order is now 1, 61, 60, 0 for modules, 60, 61, 0 for files) - In order for the Kernel to recognize these new Slots as being mappable for Modules, it must be updated to the 6.5 codebase. This is where the 6.5 nk.exe comes in, and why it's so important.
Profiling Virtual Memory is an important job for an OEM - the less available in Slot 0, the sooner a device will kick back out of memory errors (even if it's not truly out of memory) - and the worse the user experience will be. Some ROM's I have seen have less than 20MB available in slot 0 (and the user experience is as bad as you might imagine) - There are many more intricacies to the whole process - like balancing the load between services.exe and device.exe to best utilize the 32mb VM space available to each, and storing all resource-only dlls as modules so they can be allocated to Slot 63, etc.
This is also why it's important that the re-alloc tools be updated to support the new slots - g'reloc will not ever try to allocate modules to slot 60/61 because as far as it's aware, this is not possible. For the moment I know of 2 tools that will realloc to slot 60/61, wmreloc 2.0, and bepe's Platform Rebuilder (used by ervius vk)
What's the take-home message about VM?
Keep Slot 0 as free as possible. WM 6.5 NK allows you to use more modules without taking up SLOT 0 space, so allows more flexibility to use modules (which are faster to load)
Click to expand...
Click to collapse
Captain_Throwback said:
Thanks Leo, but EVK comes with this version of WMReloc. I've tried using it to cook a 6.5 "old-style" ROM, and while the ROM compiles successfully, it won't boot. I'm thinking it could be related to module overlaps due to WMReloc's not handling the 6.5 modules properly (even though I know it's supposed to). In fact that may not be the case, but I thought EXTReloc was supposed to a better job of this. I think the real issue (and I may have already stated this) is that the DSMs from the EXT packages aren't being properly re-created during the build process by DSM Editor (perhaps that's outside the realm of what it can do?). In most cases, my EXT packages have been dumped from official ROMs, and as such have the DSM/RGU's outside of the "files" folder. They should be easily re-integrated during cooking, but I don't think that step is taking place. Perhaps it's as simple as adding a command into the batch file to copy those files into the "dump" folder for each package (I'm not really sure the best way to do that, though)? And what about packages that happen to be missing that information? Is there a way to re-create those on the fly, or would that need to be done manually? I assume for custom packages (like graphics, etc.), dependency information isn't really needed, but when dumping the ROM, those files won't have a home, I suppose .
Click to expand...
Click to collapse

Just as an aside info..... the evk dont uses DSMs i mean they are useless at this point for the kitchen... maybe next generation kitchens will tell you... "Hey if you need to cook this Module for this App you need to add this and this and this due to dependencies"

Hi All
How to apply All_packages_to_one after Extreloc?
Any ideas?