yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Apps and Games] cyberde:
Probably because you've set your language to English? Try setting the manila language also to english and it will detect the XML.

Please do note that I'm no longer maintaining the app since I've got a HD2 now and I'm unable to test the app anymore...
[Windows Mobile Apps and Games] Alexboooom:
i hope it works....thnxxx
[Touch Viva, MDA Basic ROM Development] BesFen:
Updating visual kitchen with new build

SOURCE OF HOT BUILD

If you want to Build a new ROM with The new Build, go to here to get the Source.

http://xdaforums.com/showthread.php?t=544445

UPDATING VISUAL KITCHEN WITH NEW BUILD

We assume to update my 21844 visual kitchen for OPAL with newer Build (example 23037).

A. EXT

1. In the EXT\Opal create a new empty folder with the name of the build (example 23037).

2. copy the folder “Opal_External_Packages” inside EXT\Opal\21844 to EXT\Opal\23037.

Now your extended packages is ready

B. OEM

No need to modify this Folder

C. ROM

1. In the ROM\Opal Folder, create a new folder with the name of the build (example 23037). Copy the OEMXipKernel folder from ROM\Opal\21844 into this folder as shown below:

2. in the ROM\Shared Folder, create a new folder with the name of the build (example 23037). Copy the MSXipKernel folder from New Build into this folder as shown above.

D. SYS

In the SYS Folder, create a new folder with the name of the build (example 23037). Copy the SYS from the new Build into this folder as shown below:

DUMP XIP.BIN TO GET MSXIPKernel

TO make a new build ROM, we need MSXIPKernel, and sometime people only provide xip.bin of the new build. If it happens we need to dump it to get MSXIPKernel, download that file, and dump it with XIPPort.exe, here is the tools.:

http://www.4shared.com/file/125449740/a1b9e454/XIPPort.html

Now, put the attached file and the xip.bin in the same folder, then run XIPPort.exe, click “dump xip.bin” and wait until folder “OUT” appear, then click “make pkgs”, close the XIPPort.exe.

Go to folder “out” and you will find “Files and Modules” folder, inside each folder, you will find folder MSXIPKernel. Move the module inside OUT\MODULES\MSXIPKernel to OUT\FILES\MSXIPKernel, now you have the MSXIPKernel. And don’t forget to delete any *.txt file inside MSXIPKernel.

USING VISUAL KITCHEN

After add new build, run the kitchen, and you will get pic as below:

1. Choose your device, Opal

2. Choose your XIP Build

3. Choose your SYS Build

4. Choose your EXT Build

The default compression is XPR, you can make LZX compression by select the LZX.

You can change the PP, click "Other" Buton, you will see pic below:

Enter the number of PP as you want, the default for Opal is 12Mb, More PP make the ROM more stable and multitasking, you can make experience for the number of PP.

You can weather the package in the EXT, OEM, or SYS to include in the ROM or no by double click the name of packages.

OK that is all, you ready to click the "Create ROM" Button.

HAPPY COOKING :D:D:D Time to SLEEP....
[Touch Viva, MDA Basic ROM Development] BesFen:
Useful tools

USEFUL TOOLS

EXT PACKAGES CREATOR'S TOOL

http://xdaforums.com/showpost.php?p=4489567&postcount=17

http://xdaforums.com/showpost.php?p=4714566&postcount=69 Thanks XirXes

Here is some method posted by XirXes to minimize memory leak by make SLOT 0 memory free from Modules, Thanks XirXes.

Original posted by XirXes

Here some source of SYS, ready to use in VK Kitchen.

http://xdaforums.com/showthread.php?t=587655 =====> Already Recmod/convert to file

http://xdaforums.com/showthread.php?t=551470 =====> some build of SYS already Recmod/convert to file
[Touch Viva, MDA Basic ROM Development] vigos:
Great BesFen, really good work! Can any mod make this post a sticky? Thanks!

I will be trying this kitchen soon...
[Touch Viva, MDA Basic ROM Development] XirXes:
I have successfully cooked a booting 23041 rom with this kitchen and once its working right I'll make a thread for it. Thanks BesFen, you're the man.
[Touch Viva, MDA Basic ROM Development] BesFen:
Nice to hear that the kitchen work well, Now time for you and others to build ROM and share it in Forum.

GO A HEAD, MAKE A ROM....
[Touch Viva, MDA Basic ROM Development] lkachun9129:
how to solve the following error?

**Sorry for not related to your kitchen**
[Touch Viva, MDA Basic ROM Development] BesFen:
You can convert some modules to files.

If you can, try to make 0 module in slot 0 by convert some module, it will very good in releasing memory management and avoid "not enough memory" happened in your device.
[Touch Viva, MDA Basic ROM Development] theglen35:
Something wrong

Hey guys thanks for all your work on making this kitchen.But i think something is wrong somewhere.I build a rom 23037 and it booted and came up to the home screen,it has good speed but no backgroung,the home settings does not work,comm manager don't work and some other settings. What could be wrong?

Oh and i noticed that on boot the ONBL is 1.27.0000 and the OS is 1.26.0.0.
[Touch Viva, MDA Basic ROM Development] theglen35:
100% working

Guys i figured out what was wrong.The EXT folder don't have all the files for the Opal to work correctly.You can download the files from here : http://rs415.rapidshare.com/files/148930538/Opal_Stock_ROM_OEM_Folder.rar

I replaced all the files in the EXT and OEM folder with the ones i downloaded, build the rom and everything works great.By the way the SYS and XIP has to be 96dpi for it to work on the opal.
[Touch Viva, MDA Basic ROM Development] BesFen:
That's GOOD, This is we call THREAD for OPAL DEVELOPMENT, I hope everybody can share every knowledge in COOKING here.

Take a look others thread, they blow very quick, come on, i want to see other guys active here.

Transfer knowledge, Discuss, and Release a ROM.... Make OPAL FORUM HOT
[Touch Viva, MDA Basic ROM Development] TheRem:
how do i use this?

i just want to remove some apps from the rom like TouchFLO, Opera, Voice Commander etc... the ones i don't use to free up some memory.

is it like Bart PE Builder?

if i ʞɔnɟ up the cooking, will it brick my Viva when i flash it?
[Touch Viva, MDA Basic ROM Development] BesFen:
You can double click the app name from the kitchen list, or you can remove the folder name of app from EXT Folder.

The PDA may not boot (Brick) if:

1. the different version of XIP and SYS to far.

2. you don't put complete xip's files

But you can fix it by flash with others ROM, just go to Bootloader or Tricolor (I don't know which Button must press in Opal), connect your PDA to PC, and Flash again, very simple.
[Touch Viva, MDA Basic ROM Development] TheRem:
thanks BesFen! :)

i gotta try this.
[Touch Viva, MDA Basic ROM Development] nguoc:
ROM create is running, but very slowly. Looks like a fresh ROM. Btw, when I dump a cooked rom, it stop with error, may be protected ROM! Anybody know how to overcome that?
[Touch Viva, MDA Basic ROM Development] Diagrax:
Including Other Apps

Does anyone know how to add Apps (.cabs) to the list on the Kitchen so its included into the ROM like other apps not included.
[Touch Viva, MDA Basic ROM Development] BesFen:
Here the tools:

http://www.4shared.com/file/131050367/e9febb08/Package_Creator.html

Put the tools and cab file in the same folder:

1. run package-creator-v2.7.exe, Click "Open Cab File", navigate to the cab file.

2. run OLD2NEW.bat
[Touch Viva, MDA Basic ROM Development] BesFen:
Protected ROM can not be dumped, better you dump a stock (Official) ROM.

The ROM should run fast in opal, not slow, pls inspect the xip and sys, maybe you miss some module/file, or put the module not in right place.
[Touch Viva, MDA Basic ROM Development] Diagrax:
Thanx but where should i place them
[Touch Viva, MDA Basic ROM Development] nguoc:
Thank you,

I follow all the instruction in http://xdaforums.com/showthread.php?t=554858, dump the orginal rom 6.1, built a rom, then I want to dump the created rom, but cannot!

The instruction does not mention anything about xip, cause the kitchen create it during building process. So just the sys. I download the sys in

http://xdaforums.com/showthread.php?t=544445;

ported it in the kitchen, change the dpi to 96, res to 240x320, then create. But some time the ROM can boot, some time it cannot. Btw, if it boot, I found lots of errors, and don't know how to resolve it.

Does anybody have a stock 6.5 ROM or every thing dump from it?
[Touch Viva, MDA Basic ROM Development] nguoc:
Anybody know how to check the ROm without flashing it to the devices?
[Touch Viva, MDA Basic ROM Development] BesFen:
Inside EXT, like other packages, for example if you use 21844, put it inside:

\EXT\Opal\21844\Opal_External_Packages
[Touch Viva, MDA Basic ROM Development] BesFen:
read it again, Post 2nd section C. ROM

Inside folder ROM is the XIP. You have to use the right XIP and usually the number build is same with the SYS. You don't need XIP.BIN, just MSXipKernel, put it inside ROM folder like i mention in the tutorial.

The error happens because you use WM 6.1 XIP, and it's not compatible with wm 6.5.
[Touch Viva, MDA Basic ROM Development] Diagrax:
ALSO Bes...By changing the XIP to Wm6.5 will that also change the nk.exe to 6.5?:confused:
[Touch Viva, MDA Basic ROM Development] BesFen:
No, don't change nk.exe. Nk.exe is device related and it in the OEMXipkernel, don't change that or your device will not boot. you just need to replace MSXIPKernel with your current build number.

As I know, No one make a native nk.exe WM 6.5 for Opal, so you still can use WM 6.1 nk.exe.
[Touch Viva, MDA Basic ROM Development] nguoc:
Thank you.

I put the new package there, build the ROM. OK but when I Flash, no change! The new packages seem not to appeared in the new ROM!
[Touch Viva, MDA Basic ROM Development] nguoc:
Anybody know how to modify the registry before created the ROM? For example, how to change some setting in registry of the ROM, create a link, change the date and time of the ROM created, the time zone etc..

Thanks.
[Touch Viva, MDA Basic ROM Development] Diagrax:
But if we have a Wm6.1 nk.exe won't a wm6.5 ROM be unbootable?

also when we port a XIP do we have to recreate the os.payload?
[Touch Viva, MDA Basic ROM Development] Diagrax:
How do i Fix the "Can't Open XIP.bin File"?...ive tried but fail many times...i can't even port a new XIP
[Touch Viva, MDA Basic ROM Development] funguru:
Packages Saved Successfull and inserted into Rom!!!

534 Modules present; with 6.1 NK.exe Max Modules is around 535 for this ROM! btw, bootable ROM will be created!!!

NO-SPLIT mode ROM...

Modifing Lang on bat file...

deleting old bat...

Writing new bat...

Done...

Wait some seconds...

Executing Processes..... wait.....

Executing: platformrebuilder.exe.....

PLATFORMREBUILDER Copyright (c) 2008-2009 bepe Feb 15 2009 22:53:49

Building for old kernel!

Build: Premium

Locale: 0409

Preparing release structure...

... done!

Collecting standard packages and initializing hives...

XIP: 2 packages

Error: 0x8000000c

Found two versions of 'initflashfiles.dat'!

platformrebuilder.exe Executed successfull!!!

done!!!

Wait some seconds...

Executing: kitchen_build_rom.bat.....

Copying OS.nb.payload...

1 file(s) copied.

ImgfsFromNb 2.1rc2

Sector size is 0x200 bytes

ImgFs partition starts at 0x00685800 and ends at 0x00686000

Dumping IMGFS at offset 0x00685800 (size 0x00000800)

Done!

ImgfsFromDump 2.1rc2

Using compression type 'LZX'!

Sector size is 0x200

Total Sectors: 0x0002

Building OS-new.nb.payload

Partition 0 (boot)

------------------------------------

build from file 'xip0.bin'

size: 0x00000000

Partition size

bytes: 0x0001F800

sectors: 0x000000FC

flash blocks: 0x00000001

Partition 1 (XIP RAM)

------------------------------------

Can't open file xip.bin

ERROR! (errorlevel: 1)

ERROR executing: kitchen_build_rom.bat

ERROR!!!

Wait some seconds...

No ''SVN'' folders present...

Restored Original config.txt...

Temp config.txt Deleted!!!

wat am i doing wrng??? new to this plz help
[Touch Viva, MDA Basic ROM Development] BesFen:
there are some possibility:

If you already convert the .cab to ext package, it could be the shortcut is not in the location, go to windows folder in the PDA, search for your app file, if you find, it mean you put it in the correct location, now open app.dat inside app packag by notepad, you should see the shortcut there, if not, make a shortcut there. You can open others app.dat for your reference.

If you can't find it in the windows folder, you put it in the wrong location.
[Touch Viva, MDA Basic ROM Development] BesFen:
Registry is in the app.reg.

Shortcut and install location of file is in app.dat, if th location of file in in windows folder, you don't need to write it in app.dat.

app.reg and app.dat is inside each package of app, and youcan edit it by notepad.
[Touch Viva, MDA Basic ROM Development] BesFen:
nk.exe is made by device manufacture and just for specific device. nk.exe opal just for opal, and GENE just for GENE, you can't use nk.exe from others type device. The location is in the OEMXIPKernel (OEM=ORIGINAL MANUFACTURE EQUIPMENT). Microsoft only release MSXIPKernell, so just change the MSXIPKernell.

if your official ROM is wm 6.1, your nk.exe is wm 6.1, it can use for wm 6.5.

My gene use nk.exe from wm 6, and it work fine.

if you want to know the different you can read here:

http://xdaforums.com/showpost.php?p=4268137&postcount=2

Yo do not need to create os.nb.payload, it generate automatically.
[Touch Viva, MDA Basic ROM Development] BesFen:
open file "Build_log.txt" in the root kitchen, search the error there, I will try to fix it if you can give it to me or write the error message here.
[Touch Viva, MDA Basic ROM Development] BesFen:
That is the error, in every rom only have one initflashfiles.dat, the location is inside:

\OEM\Opal\0409\OEM_Lang_0409

search others duplicate file and delete it.

if after it still error, do you use my default ext package and oem that provde in the kitchen? or you replace it with ext package provided by theglen35???

Pls confirm, it is very important.
[Touch Viva, MDA Basic ROM Development] nguoc:
Thank you,

But maybe mis-understand here.

I want to change the date-time of the ROM(when flashed, it show in the configuration screen), the build version of the ROM...
[Touch Viva, MDA Basic ROM Development] BesFen:
\OEM\Opal\COMMON\OEMVersion\mxipupdate_OEMVERSION_100.provxml

Open that file by notepad
[Touch Viva, MDA Basic ROM Development] nguoc:
Thank you,

I found that already, and tried to change the ROM version. I think we can change the date time here. Is that right?
[Touch Viva, MDA Basic ROM Development] Diagrax:
thanx Ben this fixed my ERROR
[Touch Viva, MDA Basic ROM Development] nguoc:
Speedup the device

I created an flashed a ROM (xip/sys 23047). I use the EXT and OEM dump from 19971 (WM 6.1 Ship ROM from HTC). It run, but very slowly. And the File Explorer required to tap for a very long time before respond.Can you help me to speedup the device?

Thanks.
[Touch Viva, MDA Basic ROM Development] Diagrax:
???

Well I can Create A ROM but its Unbootable so Ben PLease Look at My Build_Log
[Touch Viva, MDA Basic ROM Development] BesFen:
How much is your Page Pool???
[Touch Viva, MDA Basic ROM Development] BesFen:
It should include in ROM:

Package: SQLCE Excluded By ROM!

Package: SqlCeMobile Excluded By ROM!
[Touch Viva, MDA Basic ROM Development] jagan2:
Thanks

BRO thank u very much for this excellent tutorial, this is well explained plus detailed. Bro ur hard work will not be in vain also i was trying to find something like this only for making some awesome roms from my imagination. I will surely make many roms which would have all features that people want. Just downloading files for making a brand new rom. But before i proceed i have to clarify some important doughts i hope u will reply as soon as possbile because i cant wait to make a new rom for our very own cute touch viva (opal).:D

1. USING the above tools u provided i can port any rom and make it bootable for htc opal without bricking the device?

2. This means that i can use roms made for htc daimond to make a htc opal rom?

3. Through these tools i can only port or upgrade too the new version of room as it is or i can modify titanium screen start menu ie 6 mobile?

Please give detailed answers. Waiting for ur reply i cant wait till then i will be ready with a buch of new roms wallpapers skins etc.:)

And once again thanks for this tutorial i will try my best to make this opal rom development forum hot ;)
[Touch Viva, MDA Basic ROM Development] nguoc:
I set PP to 12, some time change to 15.

I can add some packages create from CAB file. It works.

I can change some setting via app.reg.

But the device seem to very slow.
[Touch Viva, MDA Basic ROM Development] jagan2:
Help

Hello plz reply to my previous question and also a major problem i was downloading kitchen but it broke in half now the 4shared link is broken:mad: when we visit that link it redirects to someother website. Plz fix it or plz upload to mediafire its the best plus it gives resume support plz do it as soon as possible i wanna make a new rom.
[Touch Viva, MDA Basic ROM Development] funguru:
I replace OEM folder with theglen35 FRM THIS URL http://rs415.rapidshare.com/files/148930538/Opal_Stock_ROM_OEM_Folder.rar
[Touch Viva, MDA Basic ROM Development] nguoc:
Can you details the process to replace it, pls.

Cause the strucre of the OEM are differ than those supplied in the .rar file.

Or just delete all the packages in Opal_External_Packages, all file in the kitchen OEM and then past the package from the .rar file?
[Touch Viva, MDA Basic ROM Development] funguru:
now i fixed it some how.. cooked my own 23047 rom. feeling gud :D next question if i want to change the icons in start,boot screen?? where shall i put them? i mean replace?? plus how to change rom date and name??? thanx for all of your help!!
[Touch Viva, MDA Basic ROM Development] theglen35:
Where did you get the Files

Hey Friend ,can you post where you got 23047 sys/xip files from,Thanks man.
[Touch Viva, MDA Basic ROM Development] funguru:
i will try bro... i have veryless bandwidth left for this month :(
[Touch Viva, MDA Basic ROM Development] BesFen:
1. No, you can't port protected ROM, better you get the source (SYS & XIP) from Da_G Thread.

2. Yes and NO, yes you can use it if you change the resolution and DPI. If you directly use without replace the Ress and DPI, your ROM will ugly and/or unboot.

3. You can upgrade, downgrade, modify, or anything to the ROM as you want
[Touch Viva, MDA Basic ROM Development] BesFen:
No Problem with the link.
[Touch Viva, MDA Basic ROM Development] BesFen:
12 MB s enought, if you want IE run smooth, set it to 20Mb

Pls inspect your ROM again, i think you miss something in the XIP, and because of that your ROM is slow.
[Touch Viva, MDA Basic ROM Development] BesFen:
http://xdaforums.com/showthread.php?t=544445
[Touch Viva, MDA Basic ROM Development] BesFen:
Start menu icon.

http://xdaforums.com/showpost.php?p=4268138&postcount=3

Boot screen, just make 240*320 pixel animated file (GIF) and change the name to animated.gif. just search that fle and replace it.

ROM name and Date:

\OEM\Opal\COMMON\OEMVersion\mxipupdate_OEMVERSION_ 100.provxml

Open that file by notepad
[Touch Viva, MDA Basic ROM Development] theglen35:
Resolution and DPI

Hey Pal ,how do you change the Resolution and Dpi from 192 to 96 ?:)
[Touch Viva, MDA Basic ROM Development] mua30:
Pals,

I had followed the 1st instructions when downloaded the kitchen, i did the following

1- extrected wm 6.1 official rom to get ext packaged

2- replaced the packages with the packegs from official rom

3- modified packages.txt

4- build the rom

when flashed it i found the following :

1- non of the packages i had put were included, just the old one

2- un able to get right menu in explorer, unable to open today plugin

3- unable to change the rom build number or os version number, i did all of this not for not finding good roms, just want to include the arabic build packages in 6.5, any one can gimme some help.!!!

thx... Mohammed
[Touch Viva, MDA Basic ROM Development] mua30:
When Adding a package through import package, after flashing the rom its stucked, any idea! pls help
[Touch Viva, MDA Basic ROM Development] mua30:
seems no body wanna give any kind of help. no problem it may be big secrets cooking roms. thx pals
[Touch Viva, MDA Basic ROM Development] BesFen:
I don't write the tutorial like you posted above, read it again in the 1st post.

1. Ok

2. How did you extract the official ROM? use the erviys tool or manual? actually you don,t need to replace the ext, you can do it by select the ext build in the ervius kitchen.

3. no need to do it, it generate automatically.

ROM build is in the OEMVERSION inside OEM, I already explain it, You can it in the previous post.
[Touch Viva, MDA Basic ROM Development] mua30:
See http://xdaforums.com/showpost.php?p=4617442&postcount=59, i did that before.

Thx Pal
[Touch Viva, MDA Basic ROM Development] XirXes:
Some new things from the Mega.

Touchflo 2d, Now with SHININESS!! [APP][QVGA][23Sep09]NEW Manila 2D v2.0 build 19191432 from HTC Mega + Other Cabs

And the newest packages here!
[Touch Viva, MDA Basic ROM Development] BesFen:
I try to find "Import Package"in the kitchen but can't find it:confused::rolleyes:

How did you import it?
[Touch Viva, MDA Basic ROM Development] BesFen:
Thanks :D:D:D
[Touch Viva, MDA Basic ROM Development] mua30:
I point the mouse on the EXT Group in the kitchen, then pressed right mouse to make the right menu appear. When its appear I find options like : Enable Group, Import Package, Delete Package.

Now Cheif, need your help :

* When adding a new package, do i have to put it in EXT\Common or EXT\OEM! As I understand it should be in Common !!

* How I can apply new core to the kitchen, I mean, if i had dowloaded new core, and opened new core version folders, how i can distribute packages to the folders!!!

Thx Pal
[Touch Viva, MDA Basic ROM Development] XirXes:
No Problem. The cabs are based off the packages in the second link. I happened to find those updated packages because of an abundance of free time.
[Touch Viva, MDA Basic ROM Development] BesFen:
I see, if you import it, you just import the file and registry, the shortcut is left in the initflashfiles.dat, you have to make the shortcut of every app that you imported manually in app.dat.

If you use Package from Stock ROM, you need to convert it firs, and ofcourse make a shortcut to.

You can find initflashfiles.dat inside OEM_Lang_0409 folder, and you can open it by notepad.
[Touch Viva, MDA Basic ROM Development] XirXes:
I found this a while ago and I thought it could be of some use here. Its a package converter. It can batch convert as many packages as you throw at it. I used it to convert those packages I posted a few posts back from OEM to EXT style packages.

[TOOL][30.09.09] TotalFire - Package Converter 1.3
[Touch Viva, MDA Basic ROM Development] BesFen:
Thank you, i will update the first page.
[Touch Viva, MDA Basic ROM Development] BesFen:
EXT PACKAGES CREATOR IN 3rd Post

UPDATE

EXT PACKAGES CREATOR'S TOOL in 3rd Post

http://xdaforums.com/showpost.php?p=4446173&postcount=3
[Touch Viva, MDA Basic ROM Development] licat:
Volume key

I cooked a rom for Opal using Ervius with core 23071 (or 23064).

At first time run (after hard reset) everything OK.

But when soft reset the volume key (up/down) not work. They become up/down menu key:mad:

Any one solve this problem? Please, Help
[Touch Viva, MDA Basic ROM Development] mua30:
Pal,

how i could disable wifi auto start in kitchen, i searched a lot, but find nothing!! also need to know wheres default comm manager in kitchen

thx
[Touch Viva, MDA Basic ROM Development] BesFen:
comm manager is in EXT package, usually it in folder call PACKAGE_Opal_CommManager, or it could be in others folder, you can search it for CommManager.exe.

wifi auto start: there is a key and value in registry for it, I am forget about it.
[Touch Viva, MDA Basic ROM Development] mua30:
Pal, I found them in oemapps, but no registry there!! can i delete commanager from there!!
[Touch Viva, MDA Basic ROM Development] BesFen:
yes you can, you can use default windows default wireless mgr, the file is wrlsmgr.exe