Hello, I decided to try to port a SYS from a spanish wm6.1 rom from diamond, so I started to read tutorials, but the result was the spected, failed...
Here are my steps:
I took the last diamond spanish rom [1.93.412.1]. I got Os.nb using nbhextract, splitted it with nbsplit (with -kaiser argument) and dumped the payload file with imgfsfromnb and imgfstodump. But I wasn't able to separate the dump in sys and oem folders with dmp2pkg (it returned me errors), so I repeated the process with an older diamond rom [ 1.37.412.2 ].
With that rom, I was able to extract the sys and oem folders. Also, I got xip.bin using rommaster tool ("RomMaster -w 5 nk.nba -x -o xip2.bin >NUL") and dumprom (dumprom xip2.bin -5 -d XIP >NUL).
I dumped the xip.bin and made pkgs with xipport.
Using the DIY kitchen, I copied the four folders from xipport (LangDB, MSXIPKernel, MSXIPKernelLTK and WinCENLS_WWE) to ROM\XIP. Following this xda tutorial I copied the .VM folder from my old sys folder to the SYS from diamond. For the OEM folder, I used my dumped OEM folder from my Spanish pharos.
Finally, I built all and flashed. It started, but when it is loading WM at the green screen, it was cropped (needs VGA to QVGA fix). After this screen, it showed a gray screen, and it doesn't worked.
Can anyone show me the errors or some links to try again?
Thanks
hi jose_sonseca, DIY kitchen don't include xip porting tool so you must do it manually using xipport.
poldo964 said:
hi jose_sonseca, DIY kitchen don't include xip porting tool so you must do it manually using xipport.
Click to expand...
Click to collapse
Good tutorial, but I got stuck on one step:
Code:
Prepare MSXip donor
Dump your donor XIP.bin (from 20758 build)
What's "donor xip"? Searching the forum, I found some references, but no downloads for it or descriptions. It must be dumped from a rom? or how can I get it?
My original diamond rom build is 19965.
Another question: some applications have DPI192 written on their folder's name in the sys folder (like windows live), so they must be vga versions, so how can I adapt them?
Thanks
... is the xip that you want to port.
Keep in mind that the addresses offset for our pharos are not the same.
The XIP start address is 00313800 and the OS start address is 00666000.
I suggest you to use my metod to insert xip_out.bin in the OS.
So, I must follow the xipport tutorial until I get xip_out.bin.
But, after that, where should I insert xip to?
I think that the MSXIPkernel and OEMXIPkernel should be inserted in SYS (ported) and OEM (original) folders in the DIY. Is it correct?
Another thing, in the xipport tutorial, it says I should delete some files from the new xip , but hd.dll.imageinfo.txt and osaxst0.dll.imageinfo.txt aren't present in the diamond xip dump. Is it normal?
jose_sonseca said:
So, I must follow the xipport tutorial until I get xip_out.bin.
But, after that, where should I insert xip to?
I think that the MSXIPkernel and OEMXIPkernel should be inserted in SYS (ported) and OEM (original) folders in the DIY. Is it correct?
Click to expand...
Click to collapse
No, you must insert the xip in OS.nb located in "\build\ROM" folder of DIY tool.
Remember that you must port only MSXIPkernel (files and modules), OEMXIPkernel contains a device specific modules and files so dont touch it
Another thing, in the xipport tutorial, it says I should delete some files from the new xip , but hd.dll.imageinfo.txt and osaxst0.dll.imageinfo.txt aren't present in the diamond xip dump. Is it normal?
Click to expand...
Click to collapse
yes if this xip is already ported from another device
poldo964 said:
No, you must insert the xip in OS.nb located in "\build\ROM" folder of DIY tool.
Click to expand...
Click to collapse
So I must insert xip.bin in WWE official pharos OS.nb and place it in "build\ROM"
poldo964 said:
Remember that you must port only MSXIPkernel (files and modules), OEMXIPkernel contains a device specific modules and files so dont touch it
yes if this xip is already ported from another device
Click to expand...
Click to collapse
That ROM is supossed to be official from HTC, I took it from HTC Diamond's wiki. So I've done the following:
Delete:
osaxst0.dll: I've deleted osaxst0.dll folder in \modules\MSXIPkernel
osaxst0.dll.imageinfo.txt: deleted osaxst0.dll.txt in \modules\MSXIPkernel(??)
hd.dll: deleted hd.dll folder in \modules\MSXIPkernel
hd.dll.imageinfo.txt: deleted hd.dll.txt in \modules\MSXIPkernel(??)
bmui.nb0 and bmui.nb0.imageinfo.txt: they're in diamond OEMXIPkernel
I'm now reallocating the modules in memory.
I've succesfully ported XIP and inserted to OS.nb in Build/ROM in DIY chicken.
After that I've renamed SYS and OEM folders in DIY to SYS.old and OEM.old.
Then, I've dumped my esn rom, to get OEM folder (oemxipkernel folder was inside) and placed it on Build, and I copied diamond SYS to Build folder.
SYS.old folder had MSXIPkernel inside, so I've taken MSXIPkernel from the modules of ported XIP, and copied it inside. Original SYS.old had also some files inside MSXIPkernel (723fb954-d931-4348-b672-82a188e587b5.dsm, 723fb954-d931-4348-b672-82a188e587b5.rgu, mxip_lang.vol and sysroots.p7b), so I copied it from Files/MSXIPkernel (ported XIP) to the new SYS.
Then I used G'reloc to adjust Slot0, Slot1 and ROM size to the new sys (01FA0000, 03DF0000 and 8FC00000)
Also, I copied shell32 and shellres modules from Shell package from the DIY SYS folder to the new sys.
Finally, I build the rom (the three bat files), and flashed it: the pda stuck at first screen with red letters.
Thanks and happy new year
first of all try to flash the OS with new xip, so you can verify if it's ported right. To do this copy the OS.nb with new xip to "DIY\Build" folder and run "3.CreateOS.bat". Now you should have ruu_signed.nbh (with new XIP) in "DIY\Flash" folder, flash it and see what happens
poldo964 said:
....what happens
Click to expand...
Click to collapse
XIP isn't working. The flash stuck 15 minutes before I shutdown it at the "smart mobility" screen.
This was my process:
I repeated the xip porting.
Dumped the part01.raw from my pharos (it haves the official ROM, 1.11.707.1 WWE). Renamed that file to xip.bin and dumped with XIPPort. Made packages and deleted the two MSXIPkernel folders from it.
Dumped the diamond ROM to get its xip.bin. Dumped it with XIPPort and made packages. Deleted the osaxt0.dll and hd.dll folders from Modules\MSXIPkernel.
Copied the two MSXIPkernel to the Pharos "Files" and "Modules".
With XIPPort, "undo", "Relloc P", and "write maps".
Code:
03e20000 - 03e2a000 L0000a000 Virtual base address of ps2fatutil.dll
03e2a000 - 03e3a000 L00010000 Virtual base address of ONDisk.dll
03e3a000 - 03e41000 L00007000 Virtual base address of HtcFsdspy.dll
03e41000 - 03e47000 L00006000 Virtual base address of ceddk.dll
03e47000 - 03e55000 L0000e000 NUL
03e55000 - 03e59000 L00004000 Virtual base address of regenum.dll
03e59000 - 03e68000 L0000f000 Virtual base address of pm.dll
03e5a000 - 03e68000 L0000e000 !!!!!!!!!!!!!!!!!!
03e5a000 - 03e5e000 L00004000 Virtual base address of cecompr.dll
Rellocated (with M'reloc to binaries and Notepad to imageinfo.txt files)
With XIPPort, "Relloc P", and "Write Maps", "build xip_out.bin" and "write xip_out.bin" to 04_Os.nb, at 00313800.
Code:
03e20000 - 03e2a000 L0000a000 Virtual base address of ps2fatutil.dll
03e2a000 - 03e3a000 L00010000 Virtual base address of ONDisk.dll
03e3a000 - 03e41000 L00007000 Virtual base address of HtcFsdspy.dll
03e41000 - 03e47000 L00006000 Virtual base address of ceddk.dll
03e47000 - 03e4b000 L00004000 Virtual base address of regenum.dll
03e4b000 - 03e5a000 L0000f000 Virtual base address of pm.dll
03e5a000 - 03e5e000 L00004000 Virtual base address of cecompr.dll
03e5e000 - 03e68000 L0000a000 NUL
Renamed 04_os.nb to os.nb and placed at Build folder. Executed the third bat file and flashed...
hi jose,
have you patched the new xip_out.bin to fit exact file size?
if no, patch it using the batch file (Fill_XIP.bat) inside this archive. If it stucks again try to repeat the procedure using the tool inside my archive. It's named XipAddrTools (by garfieldau) and it's very useful. Here you'll find how it works. Use "OUT.pharos.20757" as a reference folder.
bye
hi,
That tool is amazing compared with the manual work.
I've repeated it with xipaddrtool, modified virtual adresses with it and reallocated physical addresses with xipport, and that tool doesn't showed any "red lines" between the modules so I think that there aren't any overlapped modules.
But at first, when I load the reference out folder, in the "all" tab of xip addr tool, a lot of yellow squares appears, like that image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These yellow squares, are errors or some information? they appear even if I reallocated or not the addresses.
Also, I tried to flash your 20757 xip in the pharos os, and it works, but my ported xip is still giving problems.
thanks
can you share the "OUT" folder?
poldo964 said:
can you share the "OUT" folder?
Click to expand...
Click to collapse
of course . Here you can download it. It includes the ported xip (out folder & xip_out.bin), the original diamond xip(build 19965) and the pharos one (from 1.11.707.1 rom).
bye
the yellow line indicate that the module must be relocated. To do this you must press the space bar and the yellow disappears.
Do this for every yellow line. When you press the space bar the tool updates the imageinfo.txt with the right address, so you don't need to do it manualy. After that run realloc p from xipport and then write maps.
Follow these steps:
make a copy of "OUT.pharos.20757" folder and reneme to OUT
open xipport and "make pkgs"
inside "OUT" folder delete MSXIPKernel folder (modules and files)
copy the MSXIPKernel folder that you want to port in "OUT" folder (modules and files)
from xipport press "undo"
copy:
Code:
cachefilt.dll
cachefilt.dll.txt
hd.dll
hd.dll.txt
mencfilt.dll
mencfilt.dll.txt
osaxst0.dll
osaxst0.dll.txt
from "OUT.pharos.20757\MODULES" to "OUT\MODULES" (overwrite)
run XIPAddrTools.exe, choose "OUT" as work folder and "OUT.pharos.20757" as ref folder
clear all yellow line by pressing space bar and close
realloc p with xipport and write maps
check MAP.physical.txt and MAP.txt (no "!" inside)
"build xip_out.bin" with xipport
patch the size of xip_out.bin with Fill_XIP.bat
finally write "xip_out.bin to:" with xipport
A problem, again...
poldo964 said:
clear all yellow line by pressing space bar and close
Click to expand...
Click to collapse
On that point, I'm able to clean all the yellow squares, except one:
Press the space doesn't work for it. I tried to reallocate to 4C000 manually with M'reloc, but even that tool doesn't work. If I enter that address in o32.vbase, and press "Do it", it shows again the old value.
Looking into the imageinfo files, filesys.dll haves it:
Code:
...
o32[1].o32_psize: 00001200
o32[1].o32_dataptr: P+00264268
o32[1].o32_realaddr: [COLOR="Red"]V+[/COLOR]0004B000
..
any other module, like imgfs.dll,
Code:
...
o32[1].o32_psize: 000001B4
o32[1].o32_dataptr: P+0008FD34
o32[1].o32_realaddr: [COLOR="Red"]D=[/COLOR]01FF3000
..
I've only seen that difference, anyway, I tried to build xip ignoring that and doesn't work, so what happens with that module?
OUT folder
bye
oops soory, forgot filesys.exe... dont worry about this it should be work anyway.
have you restored the original filesys.exe before build xip? ...and have you pached the file size before write xip_out to:?
if yes maybe the xip that you want to port has something wrong, try with another build..
I've had the same problem with some xip, all perfect but it stucks in first boot screen...
woohooo! it worked, with filesys from your 20757 folder. If I take from official WWE XIP, the same error appears (but with different address).
Now I'll start to try to port the SYS...
DIY kitchen haves a MSXIPkernel folder in SYS, what files should be placed there?
bye
jose_sonseca said:
DIY kitchen haves a MSXIPkernel folder in SYS, what files should be placed there?
bye
Click to expand...
Click to collapse
no one, you can delete this folder and OEMXIPKERNEL in OEM folder too
cu
poldo964 said:
no one, you can delete this folder and OEMXIPKERNEL in OEM folder too
Click to expand...
Click to collapse
Also, the rom didn't worked until I deleted that folder.
For porting the sys, I copied the .VM folder and shell32.dll and shellres.dll (folders) from the DIY SYS folder, added all the DPI96 folders (from touch dual spanish shipped rom, same 19965 build), and deleted the respective DPI192 packages.
It worked pretty well, I've only seen these errors:
Bluetooth doesn't work properly, happens with the two radio roms, it can't be turned on or search devices...
When searching with "Add a new device" in bluetooth config, it takes a while "working" and gives a popup showing "Bluetooth hardware error". This must be a problem related to SYS, the official pharos rom with the ported XIP works perfectly.
Activesync isn't able to connect, PC software gives a error when syncronicing, doesn't allow to access internet throught activesync.
The USB massive storage driver is still working.
EnLarge Menu frequently doesn't appear. Will try with Opal version of this app if I can found that package.
"Storage Card" folder, where MicroSD is mounted, in my rom was localized (in spanish, "Tarjeta de Almacenamiento"). This isn't important. EDIT: solution
Anyway, it's speedier than the original, without removing any OEM package, 78-79 mb free RAM. I'll try to fix that errors and upload it here.
Thanks a lot for the help
Related
Hello,
I want to cook my own ROM. After I read many many sites at this forum, I found a 'polaris kitchen 1.3' that seems to be good for me.
I want to use the original WM6.1 O2-ROM as base for my 'new' ROM.
My target is the original ROM without some progs (O2 specific) an also without tomtom, 'Erste Schritte' (First Steps) and opera.
I want to add MyMobiler, and some other cabs. Also, I want to make some registry corrections.
These steps I made:
1. Extract the Updatefile with 7Zip and got the neccassary file 'RUU_signed.nbh' as I understand correctly.
2. Extract the 'RUU_signed.nbh' with this command
Code:
NBHextract.exe RUU_signed.nbh
Now, I have these files
- '00_Unknown.nb', <== Radiofile (Thanx to ianl8888)
- '01_SPL.nb', <== ???
- '02_MainSplash.bmp', <== O2 BootSplashScreen Bitmap
- '02_MainSplash.nb' <== ???
- '03_OS.nb' <== OS file which we need to split
Question1: Do I need only the '03_OS.nb'? What do i need the other files for?
3. I used this command to split the nb-File '03_OS.nb'
Code:
NBSplit.exe -kaiser 03_OS.nb
I got this:
- '03_OS.nb.payload'
- '03_OS.nb.extra'
Question2: Is it OK to use the parameter -kaiser? Remember, I will create a orbit2/polaris ROM
Question3: What are this files for?
4. now I used this command
Code:
imgfsfromnb 03_OS.nb.payload imgfs.bin
to build the 'imgfs.bin' file
5. with the following command I've created a 'dump' folder
Code:
imgfstodump imgfs.bin
This dump folder include many subfolders and files
6. I start the package tool 'PKGTool.exe' an selected the dump-Folder
The output:
Code:
[Selected Path]
C:\Extracted ROM\dump
[Core OS]
Windows Mobile-based Pocket PCs
[Versions]
SYS: 5.2.19965.1203
OEM: 3.13.0.0
OEM: 0.0.1.0
SYS: 5.2.19958.1200
NET: 2.0.7045.0
OEM: 29.6.31301.207
OEM: 29.3.31301.207
[Language]
0407 - German (Germany)
[DPI]
96
[Certificates]
CN=Microsoft Windows Mobile PCA, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
CN=OEM_UpdateCert
CN=O2___102
[Missing Manifests]
d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
723fb954-d931-4348-b672-82a188e587b5.dsm
3346da5d-3675-4a67-925e-75f623184bda.dsm
98af2d70-895d-99af-0ffc-ede71fc1186d.dsm
75bcb9fa-30b9-8705-5d86-11acd2e2c1b1.dsm
Question4: Everything OK till now?
7. Now I've selected 'tool' - 'build packages'
Inside the dump folder, I've only two subfolder 'SYS' and 'OEM'
Maybe this is the next step ... (Thanx to ianl8888)
8. Now we must dump the 'xip.bin' with this command:
Code:
RomMaster.exe 03_OS.nb.payload -w 5 -b 0x00310000 -x -o xip.bin
[The syntax recorded in the how-to page had left out the suffix "payload" ]
So I have a XIP.BIN about 3.3Mb which XIPPort.exe has dumped into \Out\Files & \Out\Modules
Question5: What to do next?
Hi,
that is exactly the same I wanna do. After you have the SYS and OEM folder the next would be to re-create the ROM folder for your kitchen. We need a new XIP. That is the point where I don't know how to continue. I have already tested to replace the original SYS and OEM with those versions I build via dumping the new O2 Germany ROM. But after trying to rebuild and flashing the ROM with the kitchen the ROM won't boot.
Therefore I asked the chefs at http://forum.xda-developers.com/showthread.php?p=2657634 to help me.
Hopefully we can take a step further.
Tom
I have already managed to build a new german rom based on the
O2 GER 3.13 released some days ago and I used the XIP 20743 from
Shayders thread to build. Had no errors in cooking but I did not
flash yet because of maybe wrong location of XIP files in the ROM.
But I have another problem with HTC ROM Tool when trying to cook
the radio 1.59.42.15 (or any other) in the ROM. The tool always states:
"The size of this file is greater than default. Do you want to assign this file?"
I said yes and it builds the rom but now I don't know if it would work
because of the warning. I tried different radio.nb files and all of them
are 17MB and all of them give the error in HTC ROM Tool when assigning
them... Is this normal?
Olioaglio
Orbitter2 said:
Hello,
6. I start the package tool 'PKGTool.exe' an selected the dump-Folder
The output:
Code:
[Selected Path]
C:\Extracted ROM\dump
[Core OS]
Windows Mobile-based Pocket PCs
[Versions]
SYS: 5.2.19965.1203
OEM: 3.13.0.0
OEM: 0.0.1.0
SYS: 5.2.19958.1200
NET: 2.0.7045.0
OEM: 29.6.31301.207
OEM: 29.3.31301.207
[Language]
0407 - German (Germany)
[DPI]
96
[Certificates]
CN=Microsoft Windows Mobile PCA, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
CN=OEM_UpdateCert
CN=O2___102
[Missing Manifests]
d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
723fb954-d931-4348-b672-82a188e587b5.dsm
3346da5d-3675-4a67-925e-75f623184bda.dsm
98af2d70-895d-99af-0ffc-ede71fc1186d.dsm
75bcb9fa-30b9-8705-5d86-11acd2e2c1b1.dsm
Question4: Everything OK till now?
7. Now I've selected 'tool' - 'build packages'
Inside the dump folder, I've only two subfolder 'SYS' and 'OEM'
Question5: What to do next?
Question6: Should I copy these folder to the kitchen?
Click to expand...
Click to collapse
I don't know how to proceed yet with the "re-building stage", but I think you are still 3 steps short of this, anyway:
we need the XIP.BIN file to use the XIPPORT.exe tool on for XIP Files\Modules. The XIP build no. I have extracted is 19965, but we are already at 20753 for the device-independent MS files
I do NOT yet know how to extract the XIP.BIN file for this. I have successfully extracted it from an Eten temp.dat file (nbh equivalent) but not for HTC ROM files.
So I think we need to do steps 7,8,9 (xip.bin, xipport, \out) yet. How to extract xip.bin ??
Then re-build with edits (whole new ball game)
Some ROM chefs (eg. Ervius, swtos, cs) are generous enough to help, I hope, as they have in the past.
ianl8888 said:
I do NOT yet know how to extract the XIP.BIN file for this. I have successfully extracted it from an Eten temp.dat file (nbh equivalent) but not for HTC ROM files.
So I think we need to do steps 7,8,9 (xip.bin, xipport, \out) yet. How to extract xip.bin ??
Then re-build with edits (whole new ball game)
Some ROM chefs (eg. Ervius, swtos, cs) are generous enough to help, I hope, as they have in the past.
Click to expand...
Click to collapse
OK, later edit:
I've figured out how to dump xip.bin
RomMaster.exe OS.nb.payload -w 5 -b 0x00310000 -x -o xip.bin
[The syntax recorded in the how-to page had left out the suffix "payload" ]
So I have a XIP.BIN about 3.3Mb which XIPPort.exe has dumped into \Out\Files & \Out\Modules
But now, when attempting "make pkgs", XIPPort.exe falls over with "could not load file or assembly" errors these tools are so prone to. A path problem (I think) that continually drives me up the wall. We need the "packages" from XIP.BIN to know which files are the OEM drivers etc specific to the Polaris.
So I'm at steps 7, 8 and 8.5 ... it's like pulling teeth
BTW, 00_unknown.nb is the radio file.
ianl8888 said:
I have successfully extracted it from an Eten temp.dat file
Click to expand...
Click to collapse
I already thought I knew your nickname from somewhere .
ianl8888 said:
OK, later edit:
I've figured out how to dump xip.bin
RomMaster.exe OS.nb.payload -w 5 -b 0x00310000 -x -o xip.bin
[The syntax recorded in the how-to page had left out the suffix "payload" ]
So I have a XIP.BIN about 3.3Mb which XIPPort.exe has dumped into \Out\Files & \Out\Modules
Click to expand...
Click to collapse
Seems to be step 8, thank you! If we are sure that this is the right way, I will insert this step8 into the first post.
But where can I find 'RomMaster.exe'? I've only the beta without the command '-b'.
BTW, 00_unknown.nb is the radio file.
Click to expand...
Click to collapse
I already inserted this into #1
I did it the following way and created a new rom without glitches.
Though don't know if it works because I don't dare to flash it
Thanks, I see that you provided a new XIP in packages
20753 in your new thread. So I decided to use this one with your kitchen and I would breakdown the
steps now with which I built my ROM. Could you
please confirm if I have done right?
1. Download and unrar Shayder kitchen with included (3,8MB) os.nb.payload and imgfs.bin (4,0KB)
http://forum.xda-developers.com/showthread.php?t=421444
(Post #8 in the thread)
2. Download and XIP 20753 from the new thread.
http://forum.xda-developers.com/showthread.php?t=427730
3. Put the extracted SYS and OEM folder from
dumped and packaged ROM of you choice into the Build folder
of the Shayder Kitchen.
4. Put the extracted MSXIPKernel and MSXIPKernelLTK
folder from Shayders XIP 20753 into the SYS folder which
was before copied into the Build Folder.
5. Start ROM.bat in the kitchen
6. Select "1 - Build"
7. Select "1+2+3+4+5" in the next screen
8. Select "0" to let it run
9. Click the green button in the Build tool
10. Close Build tool when run ready
11. Wait to finish the nbh and enjoy!
I did so and got the ruu_signed.nbh file
ready to flash... think no need to XIPport etc.
but in fact I don't know exactly as I didn't flash my rom
Olioaglio
Olioaglio said:
I did it the following way and created a new rom without glitches.
Though don't know if it works because I don't dare to flash it
Thanks, I see that you provided a new XIP in packages
20753 in your new thread. So I decided to use this one with your kitchen and I would breakdown the
steps now with which I built my ROM. Could you
please confirm if I have done right?
1. Download and unrar Shayder kitchen with included (3,8MB) os.nb.payload and imgfs.bin (4,0KB)
http://forum.xda-developers.com/showthread.php?t=421444
(Post #8 in the thread)
2. Download and XIP 20753 from the new thread.
http://forum.xda-developers.com/showthread.php?t=427730
3. Put the extracted SYS and OEM folder from
dumped and packaged ROM of you choice into the Build folder
of the Shayder Kitchen.
4. Put the extracted MSXIPKernel and MSXIPKernelLTK
folder from Shayders XIP 20753 into the SYS folder which
was before copied into the Build Folder.
5. Start ROM.bat in the kitchen
6. Select "1 - Build"
7. Select "1+2+3+4+5" in the next screen
8. Select "0" to let it run
9. Click the green button in the Build tool
10. Close Build tool when run ready
11. Wait to finish the nbh and enjoy!
I did so and got the ruu_signed.nbh file
ready to flash... think no need to XIPport etc.
but in fact I don't know exactly as I didn't flash my rom
Olioaglio
Click to expand...
Click to collapse
I also did it this way. You're right, there is a ruu_signed.nbh after all that staff has finished. But the after flashing this ROM image to the orbit it won't boot. The splash screen is shown but nothing else happens.
I think this is caused by the XIP part.
Tom
tomduke99 said:
. But the after flashing this ROM image to the orbit it won't boot. The splash screen is shown but nothing else happens.
I think this is caused by the XIP part.
Tom
Click to expand...
Click to collapse
OK, what about the 20743 version as os.nb.payload version
as downloadable in Shayders XIP 20743 thread:
http://forum.xda-developers.com/showthread.php?t=424655
(the rapidshare link). This one does not have to be copied
into the SYS folder, but copied directly into the ROM folder.
I created a rom with this one with Polaris Kitchen 1.3.
Don't know if this would boot (didn't flash it either).
Orbitter2 said:
Seems to be step 8, thank you! If we are sure that this is the right way, I will insert this step8 into the first post.
But where can I find 'RomMaster.exe'? I've only the beta without the command '-b'.
Click to expand...
Click to collapse
1) Of course I'm not yet sure that this is the right direction. But I do know that if we want to upgrade the XIP build we have to sort the \OEM and \SYS "packages" from xip.bin. These directories contain OEM drivers specific to the device (here, Polaris)
Still cannot get XIPPort.exe to "make pkgs" although it works with an Eten X500 ROM
2) rommaster.exe is found (from my memory only) in any one of the Polaris or Kaiser kitchen files. It is a very old file, though - Nov 25, 2005. You can also find it in Shayder's kitchen on the front page of this sub-forum
Perhaps there's a later version of a "rommaster.exe" somewhere ?
Olioaglio said:
OK, what about the 20743 version as os.nb.payload version
as downloadable in Shayders XIP 20743 thread:
http://forum.xda-developers.com/showthread.php?t=424655
(the rapidshare link). This one does not have to be copied
into the SYS folder, but copied directly into the ROM folder.
I created a rom with this one with Polaris Kitchen 1.3.
Don't know if this would boot (didn't flash it either).
Click to expand...
Click to collapse
If you are too unsure to test with flashing (I thought that was what HardSPL was for !!) then try to extract your own RUU_signed.nbh in full and see what you get.
ianl8888 said:
1) Of course I'm not yet sure that this is the right direction. But I do know that if we want to upgrade the XIP build we have to sort the \OEM and \SYS "packages" from xip.bin. These directories contain OEM drivers specific to the device (here, Polaris)
Still cannot get XIPPort.exe to "make pkgs" although it works with an Eten X500 ROM
Click to expand...
Click to collapse
later edit: I have XIPPort.exe "making pkgs" now. XIPPort needs to be in its own folder ( ?? )with the support dll's etc.
So now I'm at Step 9 (the unknown) with \OEM and \SYS "packages" for editing.
The base ROM I'm trying to edit is the recent release of the official HTC WM6.1 Polaris ROM. This ROM is not protected by "all-commands-to-one" etc and so is fully extractable and editable if I can figure out how.
I think the next step (likely 10 or 12 sub-steps in there) is to understand the DSM's, RGU's, HV boot files etc. There is a tool XIPAddrTools available on this sub-forum that I have some hope for in helping here
I am trying to do two things with this ROM:
1) replace the XIP device-independent files with an upgraded set (build 1995 to build 2073)
2) remove all the crap that HTC and other ROM cooks put into it - like Cube, Home, Office etc etc
In other words, I'm trying for a WM6.1, recent XIP build, very clean ROM
Maybe ...
ianl8888 said:
I think the next step (likely 10 or 12 sub-steps in there) is to understand the DSM's, RGU's, HV boot files etc. There is a tool XIPAddrTools available on this sub-forum that I have some hope for in helping here
Click to expand...
Click to collapse
There is a very useful "sticky" thread on some of this, started by udK.
Olioaglio said:
OK, what about the 20743 version as os.nb.payload version
as downloadable in Shayders XIP 20743 thread:
http://forum.xda-developers.com/showthread.php?t=424655
(the rapidshare link). This one does not have to be copied
into the SYS folder, but copied directly into the ROM folder.
I created a rom with this one with Polaris Kitchen 1.3.
Don't know if this would boot (didn't flash it either).
Click to expand...
Click to collapse
I just tested without any modifications of XIP. I used the original XIP (os.nb.payload, imgfs.bin) delivered within the Kitchen. Only copied the SYS and OEM from the O2 ROM to the kitchen and tried to build a ROM. Result is a non booting ruu_signed.nbh.
Tom
tomduke99 said:
I just tested without any modifications of XIP. I used the original XIP (os.nb.payload, imgfs.bin) delivered within the Kitchen. Only copied the SYS and OEM from the O2 ROM to the kitchen and tried to build a ROM. Result is a non booting ruu_signed.nbh.
Tom
Click to expand...
Click to collapse
My version attached. If someone wants to try...
It's a german light version of O2 3.13.207.0 ROM
without Cube, TTN, Opera, useless stuff.
With XIP 20743 cooked in as os.nb.payload with
Polaris Kitchen V1.3
No radio included. You will most likely have to flash
1.59.42.15 manually after installation of the rom.
Olio v1 GER (Rapidshare link)
Olioaglio
If been testing around with this thread and this one and made a successful rom, some how the xip files needs to be extracted, 3,4 MB is little low, cause the one i got was 3.8 MB.
I used buildos+package_tools-2.7.exe to build my package and htcrt.exe to build the rom. (i change model from KAIS***** to POLA***** to get working and flash able rom)
I will experiment more cause i need to convert raw dump to original rom for warranty
tomduke99 said:
I just tested without any modifications of XIP. I used the original XIP (os.nb.payload, imgfs.bin) delivered within the Kitchen. Only copied the SYS and OEM from the O2 ROM to the kitchen and tried to build a ROM. Result is a non booting ruu_signed.nbh.
Tom
Click to expand...
Click to collapse
Yes, the various Registry addresses change as the XIP build changes so we need to understand RGU's, DSM's etc. The uDk sticky is helpful
Because the kitchens require a "template" to re-build a ROM, I still believe that the most thorough method is to use the just-released WWE WM6.1 HTC ROM as this template. Extract it all, replace the XIP device-independent filesystem with a newer build, remove all the stuff you don't want from \OEM "packages" and re-compile.
This is struggle street maybe, but this jigsaw is a challenge.
I've downloaded a newer version from Shayder's kitchen (found here: http://forum.xda-developers.com/showthread.php?t=427962). There is another os.nb.payload template. With this version of the kitchen I was able to produce a working ruu_signed.nbh with the SYS and OEM folder from the new German O2 ROM. Encouraged by this result I then tried to change the Kernel parts from XIP 20753 and replace NETCF2 with NETCF3.5 - Result: working ROM with NetCF3.5. Many thanks to all guys helping me especially those who have developed Kitchen's, Tools etc.
At this point I have OS version CE OS 5.2.20753 but the Build is still 19965.1.2.3. Therefore the next step should be replacing the SYS parts with its equivalents from a newer Build.
Questions about this:
1. Can I use a SYS folder from another (newer) ROM without modifications?
2. How to build a ROM with German localization? Shall I only copy the language specific folders from the original ROM to the SYS-part of the new ROM?
3. Are there some other stuff? What about Registry settings for different languages?
....
I read so many threads but I'm still not sure what to do next.
Thanks.
Tom
tomduke99 said:
I've downloaded a newer version from Shayder's kitchen (found here: http://forum.xda-developers.com/showthread.php?t=427962). There is another os.nb.payload template. With this version of the kitchen I was able to produce a working ruu_signed.nbh with the SYS and OEM folder from the new German O2 ROM. Encouraged by this result I then tried to change the Kernel parts from XIP 20753 and replace NETCF2 with NETCF3.5 - Result: working ROM with NetCF3.5. Many thanks to all guys helping me especially those who have developed Kitchen's, Tools etc.
Tom
Click to expand...
Click to collapse
Yes, that's real progress.
BUT - list step-by-step exactly how you did it, please
This is the problem - many posts about being successful, very few listing the detail.
I finally found a way to overcome space issue that cause BuildIMGFS throw error when you put too many files in the ROM using captaintrip's kitchen
The repack used imgfsfromdump instead of buildimgfs which avoid the size issue and in additon can reduce the final size of flash.dio
The usage are the same with captaintrip's kitchen, I only rename the bat to "iPAQ61x_91x flex kitchen" since this works for both 61x and 91x
You will need to rename flash.dio to TEMPLATE.ROM and put it under ROM folder, when you run iPAQ61x_91x flex kitchen.bat it will also prompt you,follow instruction
keep in mind if you use flex kitchen to build your rom won't be able to extract it properly, anyone want to edit your room will need your kitchen instead. If you don't have buildimgfs issue you may want to stick with the old way of building rom
use iPAQ614c Rom Kitchen.bat if you want to build your rom in old way
Updated July 7th: attached new cecompr_nt.dll that fixed memory leak, necessary for LZX compression, replace the one under TOOLS folder
Download (v0.3):
mediafire
Updated: Dec 9th ,09
v4 Beta:
-improve ability to decompose ROM, however the packages in SYS and OEM portion is usually mix up so you have to manually move them to correct folder after extraction
Download:
21501 kitchen
21215 kitchen
Rom folder for w version for 21215 (Rename it to ROM if you want to build w version)
21232 kitchen
21234 kitchen
21725 kitchen - removed due to too many issue, use 21728 kitchen instead
21728 WWE Kitchen
21728 ITA Kitchen
21728 GER Kitchen
21728 FRA Kitchen
21812 WWE Kitchen
21815 WWE Kitchen
23001 WWE Kitchen
23001 CHT Kitchen
23004 WWE Kitchen
21921 WWE Kitchen
23009 Hybrid WWE Kitchen
23016 18.1 WWE Kitchen
21854 WWE Kitchen
23047 WWE Kitchen
23052 WWE Kitchen
21867 WWE Manila 24M2 Kitchen
21869 WWE Kitchen
21869 WWE Manila 25M Kitchen
23088 WWE Kitchen
28002 WWE Kitchen
28011 WWE Kitchen Beta 29
28011 WWE Beta 29_2 Kitchen - kitchen of Beta 29.2
note: you can replace WinCENLS_Lang_0404 with WinNLS_WWE (from other rom kitchen) to save ROM space
-arcsoft streaming player & codec can be removed if you don't need them
23515 xip (use with 23518 SYS)
23518 CHT Kitchen (LZX)
23518 WWE kitchen
21888 WWE Kitchen
23529 WWE Kitchen
28230 WWE Kitchen
23544 WWE Kitchen
23563 WWE Kitchen
91x 28011 WWE Kitchen -not tested since i don't own 91x device so use as your own risk, use dnw in the worst case
91x 23518(23515)/21888 untested xip
Official WM 6.5 Tookit/SDK/Emulator: here
FCC Information for 610c
FCC information for 910c
----------------------------------
Structure Overview
XIP is the kernel, this is also what you see those 2xxxx build mean, the whole term is called "Execute in Place", i.e execute files in rom directly without copying to ram, this is for boot process, anything wrong mean you will stuck in clean boot
OEM is for device/manufacturer specific program/drivers
SYS is for Windows Mobile system files
A package is a folder with at least a dsm file,all other files are extra
-rgu file is just reg file which you can use notepad to edit
-default all files goto Windows directory (obviously exclude rgu file)
-initflashfiles.dat/txt is a text file with instruction to move files to different directory
Files vs Modules
Modules are folder with ".dll" in their names. Inside the folder there is imageinfo.bin, S00X where x is a digit. When they are cooked into ROM they will become dll with proper relocation (done by WMReloc/G'Reloc). Supposedly being modules would make them load faster(because no need to relocate at runtime?) and some dlls must be in modules or else some program will not work properly. However there are also cases that modules must be converted to files.
Technically you can put everything in SYS since at the end buildOS will merge everything together but it is easier to manage if you follow the OEM/SYS structure
Common Issues TroubleShooting
hang on 1st boot screen (HP Logo)
-XIP porting issue, .rom , .vm file not correct .etc
hang on 2nd boot screen (WM splash screen)
-module did not relocate properly (did you run WMReloc or GReloc?)
-XIP (lower possibility, i don't think it affect..just in case you should keep in mind)
hang/crash on today screen
-software conflict/missing .etc , check your SYS/OEM files
Endless HP update/customization engine
-happens because of different model uses different customization engine, using one from other model/region will cause it to rerun every boot time, the only solution seem to prevent it to run from start by removing it from initflashfiles.dat. Convert all the fix into packages and integrate to the rom instead
installed SIP(virtual keyboard) cannot be switched
-use recmod (under tools folder) to convert all modules into files in browsingie folder
cannot compose new sms/email .etc
-replace redist_lang_[lang_code] folder with one that worked before
wifi cannot turn off after boot
-set HKLM/Comm/SDIO86861/Wireless to 1
XIP
To insert ported xip, run this command: osnbtool -c TEMPLATE.ROM 1 xip_out.bin
where xip_out.bin is your new XIP file
xip porting tutorial can be found all over the place in xda/ppcgeek .etc
Also make sure in ROM folder, the boot.rgu is from your device xip (the kitchen I provided only contains 61x xip so to cook for 91x you need to put 91x boot.rgu instead)
Phone Radio
rilgsm.dll is needed but usually it is in OEM folder
PagePool
Overview: xda wiki
edit using pagepool_by_wlodixon under flash folder, copy your flash.dio and run the appropriate cmd
The only exception is if the rom set pagepool to 0 (Dynamic PagePool), it won't able to recognize and you have to hex edit
hex edit the xip.bin at 0x000A75E4, change all 4 bytes to your desired value (all 0 for dynamic pagepool)
Convert cab to OEM
get package creator here
use it to open cab, then wince cab analyzer opened, choose extract folder icon, after close wince cab analyzer, you will be present with shortcut screen, do you things and hit done, finally hit complete package unless you want to change some option
Create simple cab for file/reg changes
get QuickCab
Xt9
corresponding lang files in OEMApp/OEMLang_#### where #### is the 4 digits lang ID
-[2letter langs code]hpd.ldb
-[2letter langs code]lbUN_xt9s/lsUn/.etc].kdb
-et9.SQR.[Language].bmp [Optional, some language like Polish/Portuguese just point to english bmp in registry]
-[a bunch of number/digit known as GUID].rgu (if you open it up you will find there is registry on xt9)
also under OEM\OEM_Lang_[Lang number]
-initflashfiles.dat (actually you can use notepad to open it and seacrh for ldb/kbd/bmp to see which lang files )
cooking different language
-you will need your language OEM folders from original HP rom
-your language wince.nls
-replace all language mui (e.g 0409=English) with your language mui
-some languages may added extra folders, be sure to copy them into SYS too
-sometime the hp customization/update will end up endless run in every start, in this case you will need to prevent it from running and integrate all updates into the ROM
OptionXML Addon
I have written this small .Net 3.5 App to generate option.xml for SYS packages which will allow you to select the common package and different language more easily without moving folders all the time, just unzip the zip to kitchen which will overwrite the existing batch file and put the exe under TOOLS folder.
To select/UnSelect a category in BuildOS, you can click on the Category group (e.g click on 0409 will select all 0409 packages in SYS), then click on one of the packages will select/unselect the whole group
Reserved for extra space in case
-------------Step by Step guide for xip porting-----------------------
Make sure you read this tutorial first
1. copy(either get it from kitchen or dump it using osnbtool) the existing xip_out.bin and rename it to xip.bin, open xipport, click dump xip.bin and you will get a OUT folder
2. choose write map then make packages , now rename this out folder to some other name
3. dump the new xip(from other device) using osnbtool, rename it to xip.bin & do the same as step 2 with xipport
4. now copy MSXIPKernel & MSXIPKernelLTK under Modules and Files folders from OUT folder(from step3) and overwrite to corresponding 61x OUT folder(from step1)
4.5 as said in the xda tutorial, remove hd.dll, osaxst0.dll folders and their corresponding text files under modules to avoid physical address overlap
5. use xipport to undo and then realloc and write maps. Then you check map files to make sure there is no !!!(memory address overlap) I recommend using XIP address tools to check for overlap, sometime you will get error when you realloc (key already exist .etc), use xip address tool and set work folder to OUT then you will see error on first dll addr which you have to fix all highlighted red cell(overlapped address). Note that to fix first dll addr address you have to highlight the cell, enter the new start address on the V address cell in bottom, click modify, then use mouse to highlight the 1A cell above, and change the D address cell to the same as V then click modify button(on the right of V cell). You should see the change in table then. For virtual base overlap you only need to modify V cell only
Note: first dll addr overlap will result error when you click realloc in xipport.
The goal is have no overlap as shown in MAP.txt. When there is no more overlap, use xipport to build xip_out.bin and then insert the xip into the dio file using osnbtool
Commands:
extract xip: osnbtool -d flash.dio 1 xip.bin
insert xip: osnbtool -c flash.dio 1 xip.bin
also make sure your ROM\boot.rgu is from your device xip
-----------------------------------
IPAQ 91x boot keys:
Clean bOOt - Voice Commander + OK + Reset
Download Image - Volume Down + OK + Reset
Calc Checksum - Volume Up + OK + Reset - disconnected, SD card out
RUU - Volume Up + OK + Reset - UsbConnected, SDcard out
SDloader - Volume Up + OK + Reset - USB disconnected,SDcard in SDloader
Modem_CAL - Voice COmmander + Volume Up + Reset
Diagnostics - Voice Commander + Volume Down + Reset
-------------------------------------
LZX Compression:
The default compression algorithm for ROM is XPR, if you must include lots of files that causes your resulting rom >80mb under XPR(81920kb - ROM Size limit for 61x, bigger than this the device won't boot), you need to use LZX compression. It reduces rom size by ~13% but with ~1-3% performance hit(from other post I read, I never verify the performance hit).
To use LZX compression, you need to replace the cecompr.dll folder in XIP Modules with the one attached in this post. Re-port the xip (realloc + write map + build xip_out.bin) and then use osnbtool to inject the xip inot TEMPLATE.ROM.
Then hex edit the imgfs_raw_data.bin in the rom kitchen, replace the first string "XPR" without quote you found with "LZX" without quote.
Make sure you have replace the cecompr_nt.dll under tools folder of the kitchen with the one I attached in 1st post to avoid memory leak
Now just build normally, you will notice the time to inject file will take much longer because of the compression
Is there any ROM kitchen tools for hp iPAQ h6365 WM2003?
Wow great kitchen. Thanks for sharing.
here, here! keyx you da man
One thing though - when you say this:
Phone Radio
if you are using SYS from other device, make sure you replace ril.dll and phone.dll from a working rom in phoneRedist or you will get a phone radio not installed which disable phone function
rilgsm.dll is also needed but usually it is in OEM folder
Click to expand...
Click to collapse
I'm not sure that is actually correct. I've been using ril.dll and phone.dll from all kinds of donor SYS; these are OS files that should be generic. It is only rilgsm.dll that is manufacturer-specific.
you are right, I corrected the post
I think I do anything wrong...
If I extract your ROM(WM 6.5 Beta 3.81) and put it together to a ROM again, it is 10MB smaller.....After extracting this, its 1MB smaller...
Question is, why?
Greets
chucknican
actually for unknown reason if you use my kitchen to build rom, you won't able to extract it properly...i am not sure why. But currently it is the only solution for me to overcome buildimgfs error
so the solution is that I use captaintrip's kitchen to extract and yours to build it together again?
I can't get this kitchen to build my ROM. The after WMReloc does the modules rebase, I get the following feedback...
Code:
Injecting files ...
Input file imgfs_raw_data.bin cannot be opened. Exiting.
In fact, when I watch the temp folder during this process, I see no imgfs_raw_data.bin at all. In your new script, I can't see where this file would come from anyway.
Help?
chucknican said:
so the solution is that I use captaintrip's kitchen to extract and yours to build it together again?
Click to expand...
Click to collapse
no in fact i will need to upload a kitchen as the result rom using my flex kitchen will not be extracted properly
benjaminries said:
I can't get this kitchen to build my ROM. The after WMReloc does the modules rebase, I get the following feedback...
Code:
Injecting files ...
Input file imgfs_raw_data.bin cannot be opened. Exiting.
In fact, when I watch the temp folder during this process, I see no imgfs_raw_data.bin at all. In your new script, I can't see where this file would come from anyway.
Help?
Click to expand...
Click to collapse
you have to run "prepare_imgfs flash.dio -nosplit" to get the imgfs_raw_data.bin first, this process is done when you extract a rom before but if you just directly use it to build a rom you need to manually run the command on a flash.dio first
Also keep in mind if you use flex kitchen your rom won't be able to extract properly, anyone want to edit your room will need your kitchen instead. If you don't have buildimgfs issue you may want to stick with the old way of building rom
keyx said:
no in fact i will need to upload a kitchen as the result rom using my flex kitchen will not be extracted properly
you have to run "prepare_imgfs flash.dio -nosplit" to get the imgfs_raw_data.bin first, this process is done when you extract a rom before but if you just directly use it to build a rom you need to manually run the command on a flash.dio first
Also keep in mind if you use flex kitchen your rom won't be able to extract properly, anyone want to edit your room will need your kitchen instead. If you don't have buildimgfs issue you may want to stick with the old way of building rom
Click to expand...
Click to collapse
So... these files go in the root folder? That's what works for me anyway. Hmm... I think this could be easily added to the script, if you ever have to release an update to the kitchen. Anyway, thanks.
21501 kitchen added on 1st post
EDITED: kitchen updated to detect missing of imgfs_raw_data.bin and extract it automatically, I also updated some tools versions
ADC and Ipaq Data Connect
Are both of these necessary? When both are installed the ADC seems to run first and configures a "Proxy Internet" Profile in the Connection Manager which lists all 3 possible connections for my data carrier, even though I can only use the internet2.voicestream.com with T-Mobile. Maybe I am not using this correctly, but once I removed the ADC, the ipaq data connection worked fine and I was able to connect to the internet without a problem. Is this all this app does, or is there another usage that I should leave it installed for?
Thank-you
you can remove ADC if you don't want it, i think it just help to setup data connections
Customization
Keyz
I have removed some of the OEMs from the kitchen, but am not sure that I modified the initflashfile.dat correctly,will you look at it for me and see (I highlighted what I have removed)? If I remove the entire last 3 lines that contain the Utility file the device does not reboot from sdlauncher when installing. When I leave the last line in it is very speedy to install and reboot, but I have the empty utility Folder in my programs folder! I also had tried to add the BSPropCab.cab to the OEM folder but cannot get it to install correctly. I saw that you had it installed in one of your previous roms along with the other 2 arc cabs. The arc cabs I can get to work, but I really dont want to put them in, just the bsprop. Is this possible?
In OEM I added Coreplayer, PdaNet, SKTools5, Live Search, Google Search and WM5torage1.9. I had to add Google Search in here because I could not get it to work by adding the original files back into the OEM App folder: In Systems I removed ADC, VOIP and One Note, replaced NETCF with NETCF3.5, and added Transcriber back in. I thought about removing WMWidgets, I use all SPB Software, but I dont understand all of its functions, I have Googled it and there really isnt alot out there about it. What I did find though makes me think Microsoft will add more function to it once the official 6.5 is officially released-So I will keep that. For me this is a very good ROM, you have done an excellent job with modifying the kitchen.
Thank-you
Sunday
Where do you test the new roms? In the device or in somekind of emulator?
gkleding said:
Keyz
I have removed some of the OEMs from the kitchen, but am not sure that I modified the initflashfile.dat correctly,will you look at it for me and see (I highlighted what I have removed)? If I remove the entire last 3 lines that contain the Utility file the device does not reboot from sdlauncher when installing. When I leave the last line in it is very speedy to install and reboot, but I have the empty utility Folder in my programs folder! I also had tried to add the BSPropCab.cab to the OEM folder but cannot get it to install correctly. I saw that you had it installed in one of your previous roms along with the other 2 arc cabs. The arc cabs I can get to work, but I really dont want to put them in, just the bsprop. Is this possible?
In OEM I added Coreplayer, PdaNet, SKTools5, Live Search, Google Search and WM5torage1.9. I had to add Google Search in here because I could not get it to work by adding the original files back into the OEM App folder: In Systems I removed ADC, VOIP and One Note, replaced NETCF with NETCF3.5, and added Transcriber back in. I thought about removing WMWidgets, I use all SPB Software, but I dont understand all of its functions, I have Googled it and there really isnt alot out there about it. What I did find though makes me think Microsoft will add more function to it once the official 6.5 is officially released-So I will keep that. For me this is a very good ROM, you have done an excellent job with modifying the kitchen.
Thank-you
Sunday
Click to expand...
Click to collapse
what do you mean by bsprop not installed correctly? if you convert it to OEM folder correctly it should work but if you leave the customization engine run on startup there is no point to preinstall bsprop since it will reinstall again from ipaq file store(unless you did not install the update before).
Also if you modify initflashfiles.dat i believe you should use hex editor to remove the FF FE header added by notepad.
Sometime when you flash a lot the device will act weird & does not reboot from flashing, you can try to clean boot it or reflash. I think you can remove all highlighted entries without issue. You may need to leave a blank line at the end of file though.
wmwidget is a widget engine that can run apps that use pie as a container/interface, for me it looks kinda like a shortcut to a webpage, msn weather/money .etc are the sample widget come with 6.5 for now. You can remove it if you don't use it.
SwimmerBoy said:
Where do you test the new roms? In the device or in somekind of emulator?
Click to expand...
Click to collapse
device only until i figure out the emulator issue
Hi Everybody, I have a good news, Ervius Visual Kitchen V 1.8.1 is working well on OPAL, and with it you can make your own Up to date ROM and Multi Languange ROM.
First and Last, I am only presenting the Kitchen, Not the ROM, so if you have any nonworking app, please don't ask me, discuss it here with others Opal Owner because I DON'T HAVE OPAL. But if you ask me about the kitchen, i will answer it.
Thanks to:
- imblfmstr for tested the kitchen
- Ervius & Bepe for the great tools and kitchen
- Olipro
- tadzio
Download Link 21844 KITCHEN:
http://www.4shared.com/file/129247993/76a618f3/ERVIUS_KITCHEN_FOR_OPAL_By_BesFen.html
CONTENT OF 21844 KITCHEN
This is the kitchen root preview in Windows Explorer:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. EXT Folder
The External packages (EXT) folder is divided into Device Specific folders and a Shared folder:
*Device Specific folders are typically used for files (packages) that should only be applied to a specific type of the device.
Each Device Specific folder is further divided into Operating System Build Version Specific folders and a Common folder.
*Operating System Build Version Specific folders are typically used for files (packages) that should only be applied to a specific build (version) of Operating System. The Common folder is typically used for files (packages) that can be installed on any Operating System build version.
2. OEM Folder
The OEM folder can contain multiple Device Specific folders.
*Each Device Specific folder is further divided into Locale Specific folders and a Common folder.
*The Common folder is typically used for files (packages) that can be installed in any locale – not specific to a language.
*Locale Specific folders are typically used for files (packages) that should only be applied to a specific locale.
3. ROM Folder
The ROM folder is divided into Device Specific folders and a Shared folder.
*The Shared folder is typically used for kernel system files that are compatible amongst devices. (MSXIPKERNEL folder)
*Device Specific folders are typically used for kernel system files that should only be applied to a specific type of the device. (OEMXIPKERNEL folder)
-The Shared folder is further divided into Operating System Build Version Specific folders. Operating System Build Version Specific folders are typically used for kernel system files that should only be applied to a specific build (version) of Operating System.
-Each Device Specific folder is further divided into Operating System Build Version Specific folders.
4. SYS Folder
The system (SYS) folder is divided into Operating System Build Version Specific folders.
*The Build Version Specific folders will often contain files (packages) specific to the device DPI (Dot Per Inch) and Horizontal/Vertical display size.
*Each Operating System Build Version Specific folder is further divided into a ROM DPI, ROM Resolution, and Shared folder – providing a significant amount of flexibility during ROM compilation.
*The ROM DPI, ROM Resolution, and Shared folders are further divided into Locale Specific folders and a Common folder.
*The Common folder is typically used for system files (packages) that can be installed in any locale – not specific to a language.
*Locale Specific folders are typically used for system files (packages) that should only be applied to a specific locale – for example, 0409 (English).
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://forum.xda-developers.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 Time to SLEEP....
Useful tools
USEFUL TOOLS
EXT PACKAGES CREATOR'S TOOL
http://forum.xda-developers.com/showpost.php?p=4489567&postcount=17
http://forum.xda-developers.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
XirXes said:
Hey BesFen, I think we need a post about memory mapping in this thread. One of the biggest things I've found that makes a rom invariably suck is poor memory mapping. It can even lead to not booting. I use this list of modules that can be converted to files from EDTP. It helped me fix my mapping issue without breaking anything. I use RightClickRecmod from this post for converting. Right click recmod needs C++ Runtimes and .NET Framework in order to work. If for any reason that doesn't work for someone they can do it from inside the kitchen itself (I've never tried it that way) or they can use a .bat script I found here.
RightClickRecmod
•C++ Runtimes
•.NET Framework
The modules that can convert to file:
Code:
AdobeFlash = ALL
AdobeFlashCodecs = ALL
BaseApps = Beam.exe, caldl.dll, calendar.exe, doclist.dll, fexplore.exe, hotvoice.exe, note_prj.dll, notes.exe, pimg.exe, shptutil.dll, VoiceBar.dll, VoiceCtl.dll and voicedll.dll
BlueTooth = bthpbap.dll ONLY!!!!
BROWSING = browser.dll, iexplore.exe and wmlview.dll
BROWSINGCORE = jscript.dll, mlang.dll and msscript.dll only.
Browsingie = ALL
BTDUN = NONE
Bth_A2DP = Avrcp_MPplugin.dll only.
Bth_HID = All except for bthidsvc.dll
GPSid = gpsid.dll
InternetSharing = ALL
MediaOS = ALL
NetCF = ALL
OS = dw.exe, dwui.dll, enrollnot.exe, machineenroller.dll, machineenrollerlaunch.exe, networkpolicycsp.dll, omadmclient.exe, quartz.dll, tcpstk.dll, tmarshaller.exe, umarshaller.exe
Phone = simsec.dll, tkitapp.exe
PhoneRedist = siclnt.exe
Redist = configmanager.dll, configmanager2.dll, obexapi.dll, obexinbx.dll, remnet.exe, syscsps.dll, welcome.exe
RemoteDesktopMobile = ALL
Shell = autotimeupdate.exe, CertInstaller.exe, fbrowser.dll, find.dll, msnsspc.dll, mstli.exe, peghelp.exe, richink.dll, rnaapp.exe, shfind.exe, sndplay.exe, taskmgr.exe, tskschcsp.dll, tskschedule.exe and tskscheduleu.exe
SkyBox = All but MyPhoneService.dll
WindowsLive = ALL but any DLL with Resource in the name.
WindowsLiveIM = ALL, unless you leave it running.
WMWidgets = unkown since I don't run any, but I imagine if you leave widgets running there should be a few.
Click to expand...
Click to collapse
Here some source of SYS, ready to use in VK Kitchen.
http://forum.xda-developers.com/showthread.php?t=587655 =====> Already Recmod/convert to file
http://forum.xda-developers.com/showthread.php?t=551470 =====> some build of SYS already Recmod/convert to file
Great BesFen, really good work! Can any mod make this post a sticky? Thanks!
I will be trying this kitchen soon...
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.
XirXes said:
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.
Click to expand...
Click to collapse
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....
how to solve the following error?
ERROR: Not enough space in Slot 0!
Click to expand...
Click to collapse
**Sorry for not related to your kitchen**
lkachun9129 said:
how to solve the following error?
**Sorry for not related to your kitchen**
Click to expand...
Click to collapse
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.
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.
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.
theglen35 said:
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.
Click to expand...
Click to collapse
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
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?
TheRem said:
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?
Click to expand...
Click to collapse
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.
thanks BesFen!
i gotta try this.
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?
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.
Diagrax said:
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.
Click to expand...
Click to collapse
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
nguoc said:
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?
Click to expand...
Click to collapse
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.
BesFen said:
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
Click to expand...
Click to collapse
Thanx but where should i place them
BesFen said:
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.
Click to expand...
Click to collapse
Thank you,
I follow all the instruction in http://forum.xda-developers.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://forum.xda-developers.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?
[WM Kitchen] OsKitchen Zero v1.33.5: The Easiest & Most Complete Kitchen (20/10/2010)
Index of this thread
(This Page) General Informations, Download links, Screenshots
Using OsKitchen Zero (Tutorial)
Moving from Ervius Visual Kitchen to osKitchen
Frequently Asked Questions
Useful Resources (Links where to find the latest Windows Mobile Builds and EXT packages)
Description
What does this kitchen do that others don't? You should ask yourself what the other kitchens do that this one doesn't because it literally does everything: importing the ROM directly from the EXE updater, detecting all the informations to rebuild the ROMs from the ROM file itself (no more messy BAT/CMD to edit to get things working), sorting the packages with the best EXT packages conversion engine available (no more EXT packages with weird names or out of place), building ROMs for different languages in the same pass picking all the correct windows mobile packages (EA/NonEA/AH/CS/Transcriber/Uniscribe/Fonts) to use, directly installing packages on the devices without having to flash each time (package installer), automatically recmodding of packages (without touching any of the original files) to allow cooking windows mobile 6.5 ROMs using older kernels, automatic manila CFC compression to save space and improve speed (and supporting latest manila builds where CFCGui has issues) and much, much more while keeping all the user interface well organized and being extremely easy to use. Start the kitchen, import a stock ROM and go! Give it a try and find out yourself how it lives up the hype or if still unconvinced scroll down to see how much simple yet complete the kitchen is by looking at the screenshots.
Features
The kitchen has the most streamlined and self-explanatory UI you can find, it can natively import and rebuild ROMs for all the devices in the supported list without having to mess with any batch/cmd files, it shows detailed informations about every Windows Mobile package and warn about conflicts and unmet dependencies, it can build multilanguage ROMs in the same pass by automatically choosing all the right localization packages required for each language, it can import windows mobile builds of any kind, convert OEM packages/CABS/HTC Hotfixes directly to EXT packages, can automatically recmod/UPX and natively compress/patch manila manila files with CFC, it automatically detects older kernels and suggests all the right packages to recmod to get the ROM working, it checks the ROM integrity while building to avoid many common user mistakes, has a lot of tweaks directly selectable with just a click from the kitchen interface, it has the most advanced search system available and much more.
Supported devices
HTC: Artemis, Athena, Blackstone, Diamond, Elf, Gene, HD Mini, Herald, Hermes, Iolite, Jade, Kaiser, Leo, Mega, Nike, Opal, Polaris, Pharos, Quartz, Raphael, Rhodium, Sedna, Titan, Topaz, Trinity, Vogue, Whitestone (CDMA variants of all phones are supported as well)
Palm: Treo Pro
Sony-Ericsson: Xperia X1 (HTC Kovsky)
Samsung: i900/i910 (Omnia) (delete the giisr.dll in the OEMXIPKernel folder or the ROM won't boot)
Asus: P565 (XDA Zest) (even thought not officially on the list the kitchen can import the NB0 ROM extracted from the ABI file with p835abisplit2)
Other devices, with caveats: as long as you have tools to convert between NB and your phone format the kitchen should work fine unless platformrebuilder doesn't support your device (I.E. it crashes). If platformrebuilder DOES NOT support your device you can still put a dummy NK.exe from another device to stop platformrebuilder from crashing (be sure the NK version (6.1/6.5) is the same) and insert your own crafted XIP.bin (there's a setting in Advanced Tweaks to use a custom xip file).
Download link
(First time using osKitchen? Read the brief tutorial in the 2nd post)
v1.33.5 All in one package:
http://forum.xda-developers.com/attachment.php?attachmentid=423263&stc=1&d=1287585346
DISCLAIMER: This software is provided "as is" and I don't take any responsibility for any damage caused to phones or anything else. I added all sorts of integrity checks I could think of to prevent the generation of invalid ROM files and so far none of the thousands of users who downloaded the kitchen reported invalid ROM files but just like when flashing any cooked ROM don't forget that there is always the risk that the phone may end up bricked (due to defective usb controllers, defective cables, defective phone memory, wrong radio file, software interfering with the flashing tools, power outages, etc).
System requirements
Microsoft .NET 2.0 (.NET 3.0 and 3.5 are 2.0 based so those work as well), already preinstalled on most computers, the kitchen won't start without it so it's easy to find out if it's missing
The following three system requirements also are preinstalled on most computers; the kitchen will warn you if they are needed so don't worry installing them unless required:
Microsoft Visual Studio 2008 runtime, required by xidump during the importing process
Visual Studio 2003 (7.1) Runtime Libraries, required by platformrebuilder to solve the "cereg400.dll cannot be loaded" error message, required by XIDump to solve the "Failed to init decompression!" error message and required by IMGFSFromDump to solve the "Unable to load compression DLL!" error message. Copy those libraries in the Resources\Tools folder and if that still doesn't work in the system32 subfolder of your windows folder (the right subfolder for 64bit systems is syswow64)
XmlLite Update Package required to solve the "Unable to load LibNB.dll" errors (only for Windows XP SP2)
Changelog from v1.33.4 to v1.33.5
Fixed os.nb file deletion issue for devices with no sectorinfo
Changelog from v1.33.3 to v1.33.4
Fixed delete shadow order entries not being saved
Implemented internal manifest management to reduce disk overhead during package scanning
Implemented detection of registry values that are found without a preceding registry key specifier
Improved file copy and file deleting speed
Changelog from v1.33 to v1.33.3
Fixed issue with packages with duplicate files causing errors in the package installer
Fixed issues on CAB files with "\." InstallPath attribute
Un-tied Calibration Data and Skip Welcome screen settings
Fixed IMGFS cache not being applied correctly
Fixed issues when installing packages registry files containing multi_sz strings with the package installer
Fixed new packages sorting issue
Changelog from v1.32 to v1.33
Fixed issue when using a drive root directory as temp folder
Fixed a localization manager issue that was causing longer startup times
Fixed some issues in CAB file folder mapping
Fixed the kitchen truncating i780/i900 BIN files
Added error messages when the DPI or MUI settings are missing on the phone
The kitchen now allows importing ROMs even when the language folder is missing (multilanguage Samsung ROMs)
Added a warning when the initflashfiles/app.dat files are not Unicode
The kitchen now reads app.dat as ASCII when Unicode characters are not detected
Fixed issue in which the initflashfiles.dat file was left locked for a few seconds during the import process prompting a retry/cancel file operation
Added detection and parsing of DPI_ EXT subpackages
Changelog from v1.31 to v1.32
Implemented total integrity check that checks all the structure of packages, modules and every single line of initflashfiles/registry files for issues. All the issues within the package will be shown next to the package name in the packages list.
Added support for variables in initflashfiles.dat, app.dat to make localization easier (because the variables will be replaced with the correct localized folder when the ROM is built). The list of supported variables can be found in the FAQ of the official osKitchen thread.
Added “RAM Drive Mode” setting to have additional cleanups performed during the build process to reduce the space usage of the temporary folder
Fixed crash when trying to open a search result file that has a defective associated application
Implemented total integrity system: every package, DSM, module and initflashfiles file will be validated for integrity and all the problems detected will be shown with an error/warning icon on the left of the package
When importing a ROM the initflashfile values are saved with the converted hexadecimal values like the generated app.dat files
When importing a ROM the progress bar will now warn of temporary folder cleanup even when the import has failed
Removed the unnecessary PackagePath attribute from the project files
Fixed the kitchen crashing when the resources folder was missing or the command line parameters were wrong
Renamed universal package converter to universal package importer
Fixed LCID validation not checking the LCID length correctly
Fixed the pagepool size patching message reporting unlimited instead of the real size
In-line comments are now maintained when the initflashfiles is split during the ROM import
When importing a ROM the initflashfiles lines that are not valid will now be commented out
Removed the %LCID% variable as alternative to %ROM_LCID% in the ROM filename
The ROM filename variables replacement is now case-insensitive and the value of the variables has any non-filename friendly characters removed
Remove Uniscribe/Transcriber mutual exclusion warning
Improved error handling during the NBH generation process
Fixed error message during build when packages contain more than one RGU file
Fixed some registry entries being unrecognized when tabs were used for spacing
Fixed the recmod messagebox appearing twice when the device is selected and no is chosen as answer
Fixed the windows mobile build importer not deleting the imageinfo.txt files in modules
Implemented a rudimentary “Install Package on device” function that allows installing a package on the device to avoid having to flash the phone for every changed file. Currently only sends the main package (no LCID/res subpackages), doesn’t apply registry entries and applies initflashfiles entries with no variables replacement.
Fixed the kitchen crashing when the packages contained corrupted DSM files
Fixed WinCENLS_Lang_RTL_0401 detected as having the wrong syntax
Fixed error messages saying that the packages had a wrong syntax on _CS packages
Fixed Danish appearing as “da-dk” and “Portuguese” listed as “Portugese”
Fixed the locale listview showing the LCID in the country code column
Now the locale combobox shows the locale name and country instead of just the LCID
Implemented automatic Unicode detection in initflashfiles.dat files
Fixed the file copy operations continuing even after the non-resumable error message
Fixed package validation not working in the universal package importer/windows mobile build importer
Added an “Expand all” context menu entry for search results
Added warning when wince.nls ends up in both XIP and IMGFS partitions
The packages issues are now listed by subpackage
The “Install Package on Device” function now also includes the subpackages, the settings to compile the packages are extracted from the phone itself and all registry values except multistring/binary are added
Removed missing DSM warnings
Implemented binary entries support in the “Install Package on Device” function and fixed temporary folder issues
Fixed duplicate DSM creation in package properties and reduced the wait before the packageproperties form is shown
Fixed error message when loading old kitchen project files
Added support for REG_NONE registry keys
The kitchen GUI is now shown before the project files or imported ROM informations are automatically loaded
Fixed the new DSMs file for SYS/OEM packages being saved with a Guid different from the registry key one
Added support for REG_MULTI_SZ on “Install package on device”
Fixed the kitchen leaving old combo box values when loading projects referencing non-existing devices, profiles or windows mobile builds
Search now removes unnecessary wildcard characters from the search string when wildcard mode is enabled to improve search speed
Renamed “Empty project” to “New project”
Fixed crashes in “Install package to device” with some SYS/OEM packages
Implemented integrity check support for boot_ms.rgu and boot.rgu files
Removed TGTool from the kitchen archive
Disabled F5 refresh during ROM generation
Implemented path variables support in the “Install package on device” function (note: the WM build on the phone must be present in the kitchen and have the build number as folder name for the localization to work)
Fixed issue with "Install package on device" function and short filenames and multiple initflashfiles files
Halved the time required for project loading and packages list refreshing
Implemented IMGFS support for unicode characters
Implemented CE variables support in “Install package to device” function
Added HTC Oboe to the devices list
The sort column order is now reapplied after loading a project instead of defaulting to sorting by name
Fixes some issues with empty DSM files
Fixed crash when using unicode package names
Added check to prevent boot.rgu and boot_ms.rgu from being present in non-XIPKernel packages
Fixed the locales combo box not being refreshed after a new ROM has been imported
Fixed issue in which the kitchen would save a DSM file with random name instead of overwriting the correct DSM file if the source DSM file was corrupted
Implemented case insensitive manila.exe/mode9 CFC patch
Completed translation entries list for ROM importer
Added tools error handling in UPX/Recmod/PNG Compression/xidump/nbimagetool/TGTool/o2Util/ImgfsFromDump/OsNbTool/Platformrebuilder
Fixed erroneous error handling in imgfsfromdump that was causing file copy error messages if the tool failed
Fixed reduced OS file generation ignoring imgfsfromdump error messages
Fixed TSW/MST management not checking that the output file was correctly created
Fixed the kitchen ignoring missing custom user tools error messages and continuing the build process
Initflashfiles parsing now parses files as UTF8 when the UTF16 BOM header is not detected
The registry file validation now checks if the REGEDIT4 header is present
Fixed the locales selection combobox not detecting new language changes during refresh
Fixed “Install to device” function copying square resolution packages for some resolutions
Fixed LCID EXT packages lacking the RGU file not being moved into the correct main package folder
Fixed registry validation generating errors about dwords where values have initial spacing/tabulation
Added translation entries for the module validation messages
The kitchen now reads partitions informations from the OS.NB file and calls osnbtool with the proper partition numbers (to support older ROMs without ULDR)
The kitchen can now extract BIN files from more updaters (Samsung i780 and others)
Added translation entries for OS.NB generation error management
Added translation entries for the registry validation error messages
Improved error messages (added categories) on the error tooltips
Added translation entries for the package validation error messages
Added translation entries for the initflashfiles validation error messages
Added translation entries for the manifest validation error messages
Added initflashfiles variables for Application Data (%CE19%) and Program Files\Games (%CE8%)
The initflashfiles entries of imported CAB files are now mapped to the correct initflashfiles variables
How to use
Once unpacked the kitchen is ready for use, as soon as you start it you will be asked to import data from a stock ROM.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tree Structure
The new kitchen structure is very simple however it requires a ROM to be imported for device configuration files to be generated. Always import a ROM for your device and start working on it.
Output - Where generated roms are saved
Projects - Where the project files are saved
Resources - Tools and other internal kitchen files, shouldn't be touched!
Sources - Contains all the files of your Windows Mobile builds and Devices
Devices
#DEVICE NAME# (You can use the name "Common" to share packages between multiple devices)
EXT Packages - All the EXT packages must go here
OEM Packages - All the OEM packages must go here
Profiles
#Device Profile Name# - Contains the "Device Informations.XML" file and all the various packages required for building the ROM
NBH Structure - Contains files required by the kitchen to rebuild the NBH correctly
OEMXIPKernel - The OEMXIPKernel with all the device drivers and native kernel must go here
NB Structure - Contains files required by the kitchen to rebuild the Os.NB correctly
ROM Parts - .ROM, .VM, imgfs-template.bin, romhdr.bin and other files needed for relocation and XIP/IMGS generation must go here
Windows Mobile Builds
#Windows Mobile Build Number#
All - The language-neutral DPI and Resolution files must go here
Common - All the language-neutral Main Packages must go here
#LCID FOLDER# - All the localized packages must go in the appropriate LCID folder
Additional files
Visual Studio 2003 (7.1) Runtime Libraries, needed to solve the cereg400.dll cannot be loaded issue: http://www.mediafire.com/?mjmmgtwmion
ImplantXIP and ImgfsToNB tools, needed for the alternative building method: http://forum.xda-developers.com/attachment.php?attachmentid=374999&stc=1&d=1281153923
Using OsKitchen Zero
What you need to know first
The first thing you need to know is that Windows Mobile is not like a desktop operating system: you can't take a ROM from another phone and flash it on a different phone model because Windows Mobile relies on an extremely specific kernel and drivers that are compiled by the manufacturer for each device model. The Windows Mobile ROM contains only the Windows folder - yes, that's right, the ROM is just the plain Windows folder with NO subfolders - while every other folder (Windows\Start Menu, Program Files, My Documents and also Start Menu links etc.) is generated when the ROM boots the first time.
Every official Windows Mobile ROM is composed of packages. Microsoft and device makers create those packages to split windows mobile and the additional software into separated components. The real "Windows Mobile" code, interchangeable between phones, is stored in packages commonly called SYS packages, while everything the manufacturer added (the drivers and the additional applications for customization) are called the OEM packages. The EXT packages are "fake" packages that the kitchen uses to overcome the limitations of standard packages (for example EXT packages are often used to build multilanguage packages without having to create a single additional package for each language).
The Windows Mobile package structure is very simple. SYS and OEM packages are identical in structure and can only contain:
A DSM file (a file that contains some package informations, for example what other packages it require or what files it contains, most kitchens usually ignore this)
A RGU file (a registry file containing the registry entries associated with the packages)
Other files or modules that compose the package: the modules are folders that usually have file-like names (meaning they have an extension) and are a different way to store executable and DLL files on the ROM.
Note: A SYS/OEM package cannot have any subdirectory with the exception of modules directories.
EXT packages - that as already said are "fake" packages that are converted to the Windows Mobile package format by the kitchen - have a different layout: everything goes into a "files" folder except the registry files (app.reg), dsm files, initflashfiles entry files (.dat) and there can be subfolders with a LCID (language-ID) code as name (a LCID is a string composed of four HEXadecimal numbers identifying a language, e.g. 0409 for US English, 040C for Spanish, etc.) to store language-specific files in the same structure (.dsm and .reg in another "files" subfolder, like for the main folder).
EXT packages are the main way custom packages or packages from other devices are distributed on websites and forums. Recent HTC ROMs contains additional informations that allow kitchens to automatically convert OEM packages to the more user-friendly EXT packages: this allows to quickly remove applications just by disabling the package; other ROMs instead have everything stored in a single package (usually OEMMisc) and require more work to remove original applications.
The only important thing you still need to know is how the rest of the filesystem structure (Program Files, My Documents, Start Menu, etc.) is created during the first boot. All the system folders are generated and populated during the first boot because, as wrote before, the ROM contains only the Windows folder. Windows Mobile has two facilities for the first-boot (hard-reset) initialization: INITFLASHFILES.DAT, a text file that is usually in the OEM_Lang folder and that only allows creating folders and copying files (Documents folders, default pictures, and most start menu entries are usually added this way) and .PROVXML files that are some XML files that can do other advanced operations (like setting registry keys, certificates, phone settings).
Usually anything you can perform with PROVXML files, that unfortunately are difficult to edit and require a large knowledge of the format, can also be easily performed using initflashfiles and registry files. You can use the app.dat and app.reg files inside EXT packages (or initflashfiles.txt and RGU files in OEM packages) to add entries to both the initflashfiles file and to the registry: the kitchen will use them properly during the building process adding the app.dat entries to initflashfiles.txt and the reg entries to the final registry (the ROM boots with a precompiled registry HV file but you'll usually never have to mess with that when using a kitchen).
Manufacturers also use some advanced proprietary post-install tools to install custom cabs, apply themes and operator configurations (e.g. AutoRun, RunCC). Those rely on TXT configuration (*config.txt) files and can cause trouble (error messages about missing files during the first boot) when removing packages or files from packages that those config file point to if you don't update them.
When you want to upgrade a Windows Mobile Build the changes in the start menu are usually so many that it's REALLY recommended to start over with a new fresh initflashfiles.txt for that windows mobile build (you can find one for each language in the Da_G's rollup threads). Since in the official ROMs the start menu entries are all crammed into the initflashfiles.txt file (the app.dat exists only in the "fake" EXT packages) you will have to either take the time to create app.dat files for each package or to copy back all the initflashfiles entries for OEM/EXT applications back after you put the new initflashfiles for the windows mobile build you changed. The kitchen will try to move the config.txt and initflashfiles entries inside the correct packages while the ROM is imported to make SYS upgrades easier.
Now that you know the basics you can proceed to the first step...
Preparing the kitchen (Importing the Device ROM file)
1. Download osKitchen Zero and unpack the ZIP archive
2. Find a ROM update file for your device: the kitchen can import the EXE from all HTC and some Samsung updaters or alternatively the raw ROM file (the main used extensions: .NBH,.BIN and .NB are supported)
3. Open osKitchen Zero and the Import ROM Wizard will open
4. Select the device you want to work on from the drop-down list, you can actually write any device name because the list is just for reference to make sure people understand that the kitchen has been tested only with those devices
5. Select the ROM update file
6. Click NEXT
Building your first ROM to make sure everything works
At this point the main kitchen window will open. Since you imported a ROM all the "Project Settings" options will only have one choice, go on and select the only available choice for all the fields (device model, device profile, windows mobile build, language) and clicking Yes in case the kitchen asks you to automatically apply recommended changes should be enough to build a bootable and working ROM. The only setting that has more than one choice is the Compression setting that if you want to have the most available space to add your programs should be set to "LZX", if you want to use another compression first make sure that your phone will be able to flash a bigger ROM file.
Now you can go ahead and build your first ROM by clicking the "Start building button": the kitchen will work for a while, then tell you that the building process has been completed and ask you if you want to open the Output ROM folder; you can then answer yes, take the ROM file that has been generated and flash it, making sure it's the right format for your phone.
NOTE: don't try importing a ROM made for other phones different than the one you want to flash because the kitchen will rebuild the ROM for the device you imported and not any other. If you flash a ROM made for another device you risk bricking your device.
Once the ROM works (if it's a supported device it should work fine on the first try, if it doesn't please report the issue here so we can help fixing it) you can start working on the ROM. So that's it, you're ready to go. If you read the "What you need to know first" you will probably already have an idea of where to start for whatever change you want to do.
Moving from Ervius Visual Kitchen to osKitchen
Open osKitchen and import the latest ROM for your device
Replace the OEM packages
Locate the folder oskitchen created in your device (it's in the Sources folder) and delete all the packages in the "OEM Packages" folder
Open the OEM folder in the Ervius Kitchen folder, locate the folder of your device and copy&paste all the OEM packages that are inside the Common and the LCID folder (0409 for english, etc.) into a folder with any name you want inside the osKitchen "OEM Packages" folder (where you deleted them). The .VM folder can be ignored.
Replace the EXT packages
Locate the folder oskitchen created in your device (it's in the Sources folder) and delete all the packages in the "EXT Packages" folder
Open the EXT folder in the Ervius Kitchen folder, locate the folder of your device and copy&paste all the folders that are inside the Common (usually empty) and the Windows Mobile Build subfolder (it's a 5-digit number) in the osKitchen "EXT Packages" folder (where you deleted them).
Replace the OEMXIPKernel
Locate the folder oskitchen created in your device (it's in the Sources folder), go in the Profiles subfolder and then in its "default" subfolder, you'll find a folder named OEMXIPKernel, delete it.
Open the ROM folder in the Ervius Kitchen folder, locate the folder of your device, open the Windows Mobile Build subfolder (it's a 5-digit number) and then copy the OEMXIPKernel folder in the osKitchen "Profile\default" subfolder (where you deleted it).
Import the Windows Mobile Build
Locate the oskitchen Sources folder, open the "Windows Mobile Builds" subfolde and delete any folder in there.
Create a new folder with the number of the windows mobile build present in ervius kitchen (5-digit number) and create three subfolders inside: Common, All and a LCID one for each language (0409 for english, etc)
Open the ROM folder in the Ervius Kitchen folder, locate the folder named "Shared", open its Windows Mobile Build subfolder (it's a 5-digit number) and copy the MSXIPKernel folder in the osKitchen Windows Mobile Build "Common" folder you created earlier.
Open the SYS folder in the Ervius Kitchen folder, locate the Windows Mobile Build subfolder (it's a 5-digit number) and proceed as following:
Everything in the "Common" subfolders of the folders that start with DPI_ goes in the "All" folder you created in the osKitchen Windows Mobile Build folder.
Everything in the LCID (0409 for english, etc) subfolders of the folders that start with DPI_ and of the SHARED folder goes in the LCID (0409 for english, etc) folder you created in the osKitchen Windows Mobile Build folder.
Everything in the "Common" subfolder of the "SHARED" folder goes in the "Common" folder you created in the osKitchen Windows Mobile Build folder.
Frequently Asked Questions
How do I share packages between devices?
Create a folder named "Common" inside the "Sources" folder and put your packages (grouped in folders like standard device packages) in the "EXT Packages" and "OEM Packages" folders
Why is the final ROM file bigger or the total and available storage space lower than when using another kitchen?
It shouldn't. The other kitchens probably come with LZX compression selected as default while instead you told osKitchen to use XPR or None compression. You can also save additional space by using the ImplantXIP building method that removes the ULDR and some other wasted space.
How do I speed up the ROM generation process?
The kitchen needs to copy a lot of data and this may be a problem on computers where the hard-drive performance is low (i.e. laptops); antiviruses, firewalls and other applications may also interfere with the process speed therefore it's suggested to keep them off while the building process to save time. The kitchen allows setting another drive as a temporary folder to speed up the ROM generation and you can use a RAM drive (if you have enough RAM) or another hard-drive to improve the process speed.
How do I translate the kitchen?
When you start the kitchen for the first time if a translation file isn't found it will be created in "Resources\Localization" with the name matching your locale code (en-US.lng for american english, fr-FR.lng for french, it-IT.lng for italian, etc.): open that file with a text editor and translate all the text that comes after the "|||" separator (the text on the left of the separator shouldn't be touched, it's used both for reference and to identify the lines by the kitchen). Remember to post on this thread the translated files if you want them included in the official releases.
How do I reduce the space used by "Temporary OS.nb"?
It's suggested not to because the file will be needed in the next kitchen versions with the internal libnb NB dumping engine that will analyze the file, generate a new OS Structure.xml and delete it for good. The kitchen creates its own reduced files and keeps them in the Cache folder: if you really want to reduce the space used by the kitchen you can take the reduced file and replace the Temporary OS.nb with it.
How do I upgrade from an older kitchen version?
Simply delete oskitchen.exe and the Resources folder from your previous kitchen folder and put the new ones included in the archive or just unpack the archive overwriting the files. If you were using a version previous to 1.26 you will have to reimport a ROM and replace the imported packages with old ones (SYS/OEM/EXT/OEMXIPKernel (with nk.exe added inside) and remember to look at how the packages are structured). If you upgrade from 1.30 or below to 1.31 you may have to move your OEM Packages in a group subfolder because now the OEM packages are grouped like the EXT packages.
What are the variables that are supported in app.dat/initflashfiles.dat? (works only with 1.32 and higher)
%SystemDrive% (/)
%MyDocuments% (/My Documents)
%MyDocuments-MyMusic% (/My Documents/My Music)
%MyDocuments-MyPictures% (/My Documents/My Pictures)
%MyDocuments-MyVideos% (/My Documents/My Videos)
%MyDocuments-Templates% (/My Documents/Templates)
%ProgramFiles% (/Program Files)
%Windows% (/Windows)
%Windows-Fonts% (/Windows/Fonts)
%Windows-StartUp% (/Windows/StartUp)
%Windows-StartMenu% (/Windows/Start Menu)
%Windows-StartMenu-Programs% (/Windows/Start Menu/Programs)
%Windows-StartMenu-Programs-Games% (/Windows/Start Menu/Programs/Games)
Useful Resources
Windows Mobile Builds
Da_G All-In-One Windows Mobile 6.5.x Builds (Strongly recommended, contains all languages and all resolutions needed for almost any device)
Latest SYSs and OEMs XDA thread (where all the latest SYS builds are posted)
Common EXT Packages
(if you have suggestions or know where to find newer versions please post them)
Latest Touch Pro 2 EXT Packages (English-only, WVGA only)
Coming soon...
Help wanted!
1. Kitchen translation
Translators for the kitchens are needed! The kitchen is now completely localizable and will generate a translation template in the Resources\Localization folder when it's started up the first time: that file can be easily edited to translate all the text of the kitchen (also include an about entry for credits) and the kitchen will validate it and keep it updated every time it's launched organizing the entries that are missing or not found. If somebody has some spare time to help me translate the kitchen in other languages please attach a translated lng file to a post so I can include it in the kitchen archive.
2. Informations about the WM6.5.X packages required for each language
In order to improve the automatic localized packages selection I need to know which of the following packages:
Code:
BronzeEA BronzeNonEA BronzeAH | CommonEA CommonNonEA | SYSTEM_DEFAULT_FONTS COMPLEXSCRIPT_FONTS | gb18030 | Riched20 Riched20_CS | SipAR | Transcriber UNISCRIBE | Webview Webview_CS
are needed for each of the following languages:
Code:
0402 BRG Bulgarian (Bulgary)
0404 CHT Chinese Traditional
0405 CSY Czech (Ceská republika)
0408 ELL Greek (Ellas)
0411 JPN Japanese
0412 KOR Korean
0415 PLK Polish (Polska)
0419 RUS Russian
041B SVK Slovak" (Slovensko)
041D SVD Swedish (Sverige)
041F TUR Turkish (Türkiye)
0424 SVN Slovenian (Slovenija)
0804 CHS Chinese Simplified
081A SPB Serbian (Latin)
If anybody knows the right packages needed for one (or hopefully more) of those languages please let me know.
nice thread but i think u should post new sys files..... iam not able to cook may be still my format is wrong so i wanted to take reference but its old further links are broken
jagan2 said:
nice thread but i think u should post new sys files..... iam not able to cook may be still my format is wrong so i wanted to take reference but its old further links are broken
Click to expand...
Click to collapse
I uploaded 28223 SYS/XIP files, if you want other builds tell me.
@AirXtreme The kitchen is great and I like it way better than Ervius' VK, but I do have some small questions though. Since the split from the original osKitchen things have been a little vague, this is what I understand of it.
OndraSter developed the kitchens core code and you developed the new gui. Both trees still exist and both trees are 'updated' to RC3, but the version number in the .exe still says RC2.7.
Second, what is the latest version? Would it be possible to include build date and changelog in the first post, so it's easy to follow the updates to the kitchen? I know it's a lot to ask, but it would help a lot.
For the rest, great kitchen!
airxtreme said:
I uploaded 28223 SYS/XIP files, if you want other builds tell me.
Click to expand...
Click to collapse
Upload 23529 and I'll give this kitchen a whirl
Cheers.
KilZone said:
@AirXtreme The kitchen is great and I like it way better than Ervius' VK, but I do have some small questions though. Since the split from the original osKitchen things have been a little vague, this is what I understand of it.
OndraSter developed the kitchens core code and you developed the new gui. Both trees still exist and both trees are 'updated' to RC3, but the version number in the .exe still says RC2.7.
Click to expand...
Click to collapse
It's because my sources are from 2.7 and didn't update the titlebar.
KilZone said:
Second, what is the latest version? Would it be possible to include build date and changelog in the first post, so it's easy to follow the updates to the kitchen? I know it's a lot to ask, but it would help a lot.
Click to expand...
Click to collapse
The last version is the one in the first post, when I'll release other updates I'll update the first post and add a changelog.
dickenz said:
Upload 23529 and I'll give this kitchen a whirl
Cheers.
Click to expand...
Click to collapse
It was already up but with the wrong name (28223), now names are fixed.
Awesome, thank you that clears it I guess. Just forgive my stupidity... Downloading the ... latest ... version now (and updating my current version).
airxtreme said:
The last version is the one in the first post, when I'll release other updates I'll update the first post and add a changelog.
Click to expand...
Click to collapse
@Airxtreme
The version in 1st post supports Iolite?
I didn't see it in supported devices list.
dancer_69 said:
@Airxtreme
The version in 1st post supports Iolite?
I didn't see it in supported devices list.
Click to expand...
Click to collapse
Yes, I think I added its device file.
I'll download now and test, thanks.
EDIT
I just checked and I allready have this version(Os kitchen 1.4 RC2.7)
and I have successfully build an nbh with this version, I just not flash it yet.
So, it's supported.
Okay,
I just download the New ATT Shipped ROM from HTC and I was going to give this kitchen a try.
I extracted the files from the shipped ROM.
When I started the kitchen, it asked me to point to the RUU file. I selected the RUU_signed.nbh that I had just extracted and I get the message "There was no os.nb present i this file! Can't continue"
What am I doing wrong?
rgb-rgb said:
Okay,
I just download the New ATT Shipped ROM from HTC and I was going to give this kitchen a try.
I extracted the files from the shipped ROM.
When I started the kitchen, it asked me to point to the RUU file. I selected the RUU_signed.nbh that I had just extracted and I get the message "There was no os.nb present i this file! Can't continue"
What am I doing wrong?
Click to expand...
Click to collapse
Give me the link to download the rom so I can try to see why no OS.nb is detected.
airxtreme said:
Give me the link to download the rom so I can try to see why no OS.nb is detected.
Click to expand...
Click to collapse
http://www.htc.com/us/support/tilt-2-att/downloads/
Third download on the list. Complete ROM
airxtreme said:
I uploaded 28223 SYS/XIP files, if you want other builds tell me.
Click to expand...
Click to collapse
Thankyou actually i wanted to test the sys xip provided by u coz whenever i try to sort sys and xip myself for oskitchen it crashes platformbuilder.exe so will try the one made for oskitchen.
But plz plz its too big file for me. I request you to upload build 23529 qvga lang 0409 only and specially on mediafire or any uploading site which supports parallel downloads. I will be waiting ....
jagan2 said:
Thankyou actually i wanted to test the sys xip provided by u coz whenever i try to sort sys and xip myself for oskitchen it crashes platformbuilder.exe so will try the one made for oskitchen.
But plz plz its too big file for me. I request you to upload build 23529 qvga lang 0409 only and specially on mediafire or any uploading site which supports parallel downloads. I will be waiting ....
Click to expand...
Click to collapse
http://www.mediafire.com/?zy0ejwmiwmy
Ok ppl as Badwolve1 (sorry bud, it was my bad '-_-) did for OSkitchen i will do it for EVK (remember that EVK is not fully updated for build ROMS for newer devices)
If you want to set the kitchen to build ROMS for newer device you must to search what you need to update the build info.
We need this things:
Go to your C:\ and select tools in the menu bar select folder options and enable to see the extensions of files.. see hiden files and see system files
Download this and install them:
Net Frameworks 3.5
MS visual 2008
Ervius visual kitchen 1.8.1
Upgrade EVK 1.8.2 (Just replace the exe)
once you get the folders of the kitchen and installed the net 3.5 and Visual redist 2008
you need to modify a lil your kitchen_build_rom.bat file that must be in the TOOLS folder.
but i will tell you how later.
!!Starting on!!
Your new Kitchen looks like this now!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once you downloaded the EVK you must to put the My Tools, Tools, and the EXE into a folder with a short name ( I use XDA) and please dont use spaces in the names of the root folder
This is the kitchen root preview: as we can saw in c:\XDA
Yes unrar it on C: and call it XDA to avoid the large name issues at CMD!
Inspecting the Facility
We must to create an estructure like this (i will just point you the folders by now, we will fill them later)
C:
-XDA
--TOOLS
--My Tools
--ROM
---<Yourdevicename>
----<Buildnumber>
---Shared
----<Buildnumber>
--OEM
---<Yourdevicename>
----COMMON
----<LangCode>
--EXT
---<Yourdevicename>
----<Buildnumber>
----COMMON
---Shared
--SYS
---<Buildnumber>
----DPI_XXX
-----COMMON
-----<Langcode>
----DPI_XXX_RESH_XXX_RESV_XXX
-----COMMON
-----<Langcode>
----Shared
-----COMMON
-----<Langcode>
Other folders like temp, release XXXXX, build log, are autocreated by the kitchen
Open your kitchen_build_rom.bat it must be on the TOOLS folder(right mouse click select "edit") and open it in wordpad to modify it... you will see this line (black line)
Code:
set ROMHDR=ROM\%device%\romhdr.bin
set XIP_PATTERNS=ROM\%DEVICE%\%xipbuild%\*;ROM\SHARED\%xipbuild%\*
set OEM_PATTERNS=OEM\%device%\COMMON\*;OEM\%device%\%locale%\*
set SYS_PATTERNS=SYS\%sysbuild%\SHARED\COMMON\*;SYS\%sysbuild%\SHARED\%LOCALE%\*;SYS\%sysbuild%\%dpi%\COMMON\*;SYS\%sysbuild%\%dpi%\%LOCALE%\*;SYS\%sysbuild%\%res%\COMMON\*;SYS\%sysbuild%\%res%\%LOCALE%\*
set EXT_PATTERNS=EXT\%DEVICE%\%EXTBUILD%\*\*;EXT\%DEVICE%\COMMON\*\*;EXT\SHARED\*\*
set DSM_TEMPLATE=%dsm%
set DSM_INCLUDES=*
TOOLS\platformrebuilder.exe
[B][SIZE="4"]if not "%errorlevel%"=="0" goto error[/SIZE][/B]
REM===========================================================================================
Modify the line write "REM" (without quotes) before the line and a space it must be like this
Code:
set ROMHDR=ROM\%device%\romhdr.bin
set XIP_PATTERNS=ROM\%DEVICE%\%xipbuild%\*;ROM\SHARED\%xipbuild%\*
set OEM_PATTERNS=OEM\%device%\COMMON\*;OEM\%device%\%locale%\*
set SYS_PATTERNS=SYS\%sysbuild%\SHARED\COMMON\*;SYS\%sysbuild%\SHARED\%LOCALE%\*;SYS\%sysbuild%\%dpi%\COMMON\*;SYS\%sysbuild%\%dpi%\%LOCALE%\*;SYS\%sysbuild%\%res%\COMMON\*;SYS\%sysbuild%\%res%\%LOCALE%\*
set EXT_PATTERNS=EXT\%DEVICE%\%EXTBUILD%\*\*;EXT\%DEVICE%\COMMON\*\*;EXT\SHARED\*\*
set DSM_TEMPLATE=%dsm%
set DSM_INCLUDES=*
TOOLS\platformrebuilder.exe
[B][SIZE="4"]REM if not "%errorlevel%"=="0" goto error[/SIZE][/B]
REM===========================================================================================
Change this line with the name of your device, (by default it says kaiser) as you can see i set -hermes
Code:
[B]set MERGILO= ..\TOOLS\IMGFS\NBMerge [U]-hermes[/U] OS-new.nb[/B]
set LOCALE=0409
set BUILD=Premium
set DPI=DPI_96
set RES=DPI_96_RESH_240_RESV_320
set DEVICE=HERMES
set OLDKERNEL=
Save the changes.
FOLDERS EXPLANATION!!!!!
EXT Folder
The External packages (EXT) folder is divided into Device Specific folders and a Shared folder.
*Device Specific folders are typically used for files (packages) that should only be applied to a specific type of the device.
-Each Device Specific folder is further divided into Operating System Build Version Specific folders and a Common folder.
ººOperating System Build Version Specific folders are typically used for files (packages) that should only be applied to a specific build (version) of Operating System
ººThe Common folder is typically used for files (packages) that can be installed on any Operating System build version.
-----------------------------------------------------------------------------
OEM Folder
The OEM folder can contain multiple Device Specific folders.
*Device Specific folders are typically used for files (packages) that should only be applied to a specific type of the device.
-Each Device Specific folder is further divided into Locale Specific folders and a Common folder.
ººThe Common folder is typically used for files (packages) that can be installed in any locale – not specific to a language.
ººLocale Specific folders are typically used for files (packages) that should only be applied to a specific locale.
-----------------------------------------------------------------------------
ROM Folder
The ROM folder is divided into Device Specific folders and a Shared folder.
*The Shared folder is typically used for kernel system files that are compatible amongst devices. (MSXIPKERNEL folder)
*Device Specific folders are typically used for kernel system files that should only be applied to a specific type of the device. (OEMXIPKERNEL folder)
-The Shared folder is further divided into Operating System Build Version Specific folders.
ººOperating System Build Version Specific folders are typically used for kernel system files that should only be applied to a specific build (version) of Operating System.
-Each Device Specific folder is further divided into Operating System Build Version Specific folders.
ººOperating System Build Version Specific folders are typically used for kernel system files that should only be applied to a specific build (version) of Operating System.
-----------------------------------------------------------------------------
SYS Folder
The system (SYS) folder is divided into Operating System Build Version Specific folders.
*The Build Version Specific folders will often contain files (packages) specific to the device DPI (Dot Per Inch) and Horizontal/Vertical display size.
-Each Operating System Build Version Specific folder is further divided into a ROM DPI, ROM Resolution, and Shared folder – providing a significant amount of flexibility during ROM compilation.
ººThe ROM DPI, ROM Resolution, and Shared folders are further divided into Locale Specific folders and a Common folder.
···The Common folder is typically used for system files (packages) that can be installed in any locale – not specific to a language.
···Locale Specific folders are typically used for system files (packages) that should only be applied to a specific locale – for example, 0409 (English).
DUMPING THE ORIGINAL ROM
We need to get any stock rom we have floating around (check the thread called shipped roms collection stickied
change the extension from exe to rar and we just need the RUU_Signed.nbh file put it somewhere in your PC
If you have a diferent language ROM than english i will suggest you to start with english lang code 0409 cause almost all the pkgs are easy to get in 0409... maybe i will make anothe rtutorial to translate that pkgs to your native lang
Here is a list of Language codes (thanks Da_G)
0401 SAU Arabic المملكة العربية السعودية
0403 ESP Catalan España
0404 CHT Chinese Traditional 台灣
0405 CSY Czech Česká republika
0406 DAN Danish Danmark
0407 DEU German Deutschland
0408 ELL Greek Ellas
0409 USA English United States
040B FIN Finnish Suomen tasavalta
040C FRA French République française
040D HEB Hebrew מְדִינַת יִשְׂרָאֵל
0410 ITA Italian Repubblica Italiana
0411 JPN Japanese 日本
0412 KOR Korean 한국
0413 NLD Dutch Nederland
0414 NOR Norwegian Bokmål
0415 PLK Polish Polska
0416 PTB Portuguese Brasil
0419 RUS Russian Россия
041D SVD Swedish Sverige
0804 CHS Chinese Simplified 中华人民共和国
0816 PTG Portugese Portugal
0c0a ESN Spanish España
Click to expand...
Click to collapse
1.- Download the newest stock rom of your Device and save it in your destop... sometimes the file is an .EXE file so you must to rename it as .rar
2.- Open the rar file, and xtract the file called RUU_Signed.nbh the others we dont need them anymore,
*3.- Put your nbh file in a folder into your kitchen root direction.. a folder called STOCK
*4.- Sometimes the RUU signed nbh is inside another exe calle RUU inside.exe do the same operation xtract it and chege the name to rar... you will find the nbh now.
Xplain IMAGES
5.- Execute your Erviuskitchen.exe.... (its no problem if the kitchen tells you that there arent some folders... of course are missing say OK to all)
6.- We must to hit the DUMP button, Search in our STOCK folder for our nbh file
7.- the kitchen will dump the rom
** the kitchen will ask you to type the name of your device
Its a huge task so let it run.... it must say dump succesfully now you will have a new folder called DUMP inside you will find more folders like a fresh new kitchen, cut the OEM and ROM folder and paste them to our main kitchen.
The OEM folder must contains a folder with the name of our device and inside it will have three folders... .VM, COMMON and 0409.
The ROM folder will contains a folder with a build number and inside a folder called OEMXIPKERNEL (this is the device's kernel (The kernel version will be accordly to the dumped rom, if you dump a WM6 rom you will have native 6.0 kernel)
the rom folder will contains three files: romhdr.bin, xip.bin and the payload... you can delete the info.txt file
Then go to the folder SYS\<buildnumber>\SHARED\COMMON\ and cut the folder wincenls_WWE and paste it to OEM\<Device>\COMMON\ this file never change and is needed to boot, so if we add it into the oem we never forget it
Now you can move the STOCK folder out of the kitchen, and our kitchen looks like this
Now you need to go the 6.5 Initflashfiles.dat repository thread and download the PKG that contains all the langs... and choose the WWE iniflashfiles.dat check the main sticky thread to locate the repository thread.
The initflashfiles.dat is the file that will set the specific 6.5 file structure, so in WM6.5 it change a lot since 6.1 and 6, so we must to overwrite the one in our folder OEM\<device>\0409\OEM_lang_0409\
Continue...
!!!!!Setting up the ROM and SYS!!!!!
First of all:
As we most know there are NATIVE 6.5 NKs but the repository thread is updating , get them here
This is just the OEMXIPKERNEL and the bin files, this is the Device Kernel Part
As you can see in the image you must to put in the ((ROM\Devicename\Buildnumber\))
the folder OEMxipkernel that is included into the native kernel downloaded file
The "XIP.bin" "romhdr.bin" and the "payload" in ((ROM\Devicename\))
(so we have now to get the MSXIPKERNEL)
The MSXIPKERNEL is the build OS specific kernel part, so...
The kitchen will takes the OEMXIPKERNEL (the native 6.5 NK) and the MSXIPKERNEL for the build to be compiled, and we could have the kernel complete. the kitchen will port the xip.bin for us.
The MSXIPKERNELLTK folder (Logo Tool Kit) Is not needed, it has just a .DSM that allows the carrier to make important fixes and upgrades to their ROMs (But they didnt use it) so we dont need it anymore.
where to get the MSXIPkernel??? go to the Latest SYSs & OEMs thread and download any build you wish to cook... there are many other threads that offers the new builds, please check the Main sticky thread of chef central HERE.
If you download a new build Rollup pkg (200 MB), you will have all the SYS pkgs and the MSXIPKERNEL inside... in one folder!
If you download a stripped build pkg (from 50MB to 70MB), you will have (maybe) all the SYS pkgs already arranged in EVK format!
I invite you to read the Da_G guide to know all the pkgs inside a rollup rar file this way you can get more info about all the pkgs.
There are many tools to set the rollup pkgs into EVK format... I like to use THIS
Here I have a video to xplain how to use it (spanish only sorry i need a translator )
lets see graphically how the SYS rollup is and how this tool make the job for us
1.- I create a folder called New Build
2.- Donwloaded the packer.jar
3.- Downloaded the rollup pkg new build 23563
4.- Unrar the rollup pkg into a folder called SYS
Then RUN the packer.jar follow the instructions as the developer of Packer.jar says in his thread
and we will have all the sys in a folder called Build (rename this folder to 23563, cause is the name of the new build number we downloaded) and now is sorted into EVK format like this...
**Note: in the packer i set lang 0409, dpi 96, resh 240, resv 320, cause my device is QVGA and i want to cook in 0409 lang.
Now we must to open the shared\common folder in our new sys 23563 folder...
We must to locate some pkgs that we will not use whats the reason to delete this pkgs? the reason if you have red the Da_G sys rollups info, is beacuse we are cooking for 0409, most of this pkgs like EA and complexscripts and sipar , msim and others are for MiddleAsia ROMS.
1.- We are cooking for 0409 se just need the pkgs with the name NonEA, so we can delete the pkgs called EA and AH.
2.- If we have Native kernel 6.5 we will use Modules instead of files so we can erase the pkgs called Baseappsfiles, Osfiles and MediaOsFiles, so we kept osmodules, baseappsmodules and mediaosmodules.
3.- delete complexscript_fonts, gb18030, msxipkernelLTK, nonephone, riched20_CS, RIL710MUX, SIPAR, MSIMAR, Uniscribe, webviewCS, wincenls_WWE (cause we already have it in OEM folder) and the xip.bin cause we dont need it.
Well, its time to create in the root kitchen folder, a new folder called SYS, and move the entire 23563 folder into the SYS folder.
as you may see in the picture, there is the MSXIPKERNEL folder...
1.- Go to your ROM\SHARED folder and create a folder called 23563, cut that MSXIPKERNEL inside SYS\shared\common and paste it to the new ROM\SHARED\23563 folder, and we will have now the OS specific part of our ROM.
2.- If you downloaded the native 6.5 kernel you must to rename the folder XXXXX (build number) to "23563" into "ROM\<device>\" so now the Device Kernel match to the OS kernel and SYS build number... that three elements are now set as 23563
And the kitchen root looks like this now:
At this point we have:
6.5.X 23563 SYS
6.5.X 23563 OS Kernel
6.5 Native Device kernel
Old OEM drivers and Main apps (you can switch to newer drivers searching for them i actually have some OLD WM6 and some NEW WP6.5 HD2 Drivers)
But what about the EXT PKGS????
You can add more today plugins, other third party apps, and/or tweaks by making EXT PKGS you can read a lot of info about this new PKGS or you can add them into the OEM\Common folder if you have OEM PKGS.
How?
Well the structure is almost the same as all in the kitchen
C:\
-XDA
--EXT
----<Buildnumber>
------COM5 Tricks
--------Beta Expiry Watermark
------BUILD IMAGES
--------Welcomehead
----COMMON
------Multimedia
--------Camera 6.0
--------HTC leo album
------Tweaks
--------NewIcons
--------Performance
--------Registry fixes
------Addons
--------Coreplayer
--------Youtube player
--------Adobe reader
--------Cfacebook plugin
Etc etc etc....
And we are good to go!!!!
WHOOO HOOOO!!!!!!!!!!!! we made it!!!!!!!!! its already set! so this is the kitchen UI, if everything was ok the kitchen launch without troubles if you saw an error check the folders it says (SVN folders don cause troubles at starting the build proces) SO just set the device, XIP, SYS EXT they must match, and select the apps to be installed or not by clickng double.
HAPPY COOKING GUYS!!!!
try it at your OWN risk IM not responsible for damages to your device
Any question about setting the kitchen please ask whatever!!! we will support you
I have here some Video tutorials in my native lang Spanish
Your noob chef +QuePPC
Video Tutorials in Spanish
Part 1
Part 2
Part 3
Part 4
Video Tutorials in English (thanks to lion75y)
http://www.youtube.com/watch?v=mn7TbHcqFgQ
http://www.youtube.com/watch?v=mn7TbHcqFgQ
http://www.youtube.com/watch?v=ptMqPd0wRBI
http://www.youtube.com/watch?v=ad42UBwUhlM
I need one more atm
I finish!!!! you can start here to ask jiji
suddnely my evk stops working..
even when i freshly insatll it it says nbhutility encounter a problem??
Unable to find wincenls_WWE
After I dump the stock .nbh, I'm unable to find the wincenls_WWE folder under the SYS_<buildnumber>_SHARED_COMMON folder. In alpha order in SYS folder it gives folders:
voice command, welcome center, windows live, WWAN
wincenls_WWE folder is not there?
I am building for Diamond(Victor) CDMA.
(Ervius Kitchen did say,
"Copying \Tools folder into new kitchen...
Kitchen builded successfull!!!
=====================================
All Done... Nbh/nb/payload Dumped and ''Kitchen'' created Successfull!!!")
edit:
I did a new dump from the stock .nbh from a Vogue(CDMA sprint touch) and found the winCENLS_WWE folder there. Can I copy that one to the CDMA Diamond one?
yes you can use that wincenls_wwe put it into oem\device\common
+ Que PPC said:
just remember, to have a booting rom, if the rom stucks at first splash screen... is XIP troubles... if the rom stucks at second or welcomehead spalsh screen is omething related to REGS
Keep in mind that you need FWupdate and wincenls_wwe in the rom! for fwupdate you can use the dummy pkg in OEM both, just to dont forget them
Click to expand...
Click to collapse
where should FWupdate and wincenls_wwe be found in the packages? I dont see them anywhere
wincenls_wwe is from your device's source(Device Specific) and FWUpdate could be either the dummy pack or an original pack from a rom's dump.
Regards!
Use the attached PKGS
The wincenls_wwe is notdevice specific... cause it contains the regional settings data.. you can use it in OEM common
The FWUpdate is EXT PKG you can disable the default fwupdate from every new SYS
If your Antivirus detects some threats in the donwload links for EVK, its not true... sometimes antivirus detects osnbtool as a virus... many ppl knows it.
for me every antivirus detect implantxip as win32
mmmm thats why i use the "None Antivirus Pro Edition"
+ Que PPC said:
mmmm thats why i use the "None Antivirus Pro Edition"
Click to expand...
Click to collapse
oh whats that
I dont use antivirus
+ Que PPC said:
I dont use antivirus
Click to expand...
Click to collapse
lol dont u risk your life from internet buddy????
or u r save by god
Hi. Thanks for the tutorial. I'm a noob in cooking.
I have been following your step by step instructions, but I faced two issues:
1. On post#3, I have downloaded the 6.5 native kernel for Topaz, where should place the files? It's not indicated in your post. Do I replace the OEMXIPKERNEL the the stock ROM dump?
2. How do I get the contents of EXT folder? I have followed every step given carefully, but my EXT folder is still empty...
Please help. Thanks!
I add that part sorry for skip it
As you can see in the image you must to put in the ((ROM\Devicename\Buildnumber\))
the folder OEMxipkernel that is included into the native kernel downloaded file
The "XIP.bin" "romhdr.bin" and the "payload" in ((ROM\Devicename\))
(so we have now to get the MSXIPKERNEL)
The MSXIPKERNEL is the build OS specific kernel part, so...
Click to expand...
Click to collapse