yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Software Development] OndraSter:
I don't have much time right now to add any devices.

I'll write how to write a new "module" for device so anyone can contribute (it is written in C#, but it is quite easy for newer devices).

If you look into original osKitchen Kaiser http://xdaforums.com/showpost.php?p=4836277&postcount=997 - in this post I posted whole Kaiser-ready kitchen. I suggest taking OEM, ROM and NK from it, so you won't miss anything.
[Windows Mobile Software Development] zeer:
more information about kitchen structure would be good.

Error: 0x80000009

'boot.rgu' does not exist in the specified paths!

where should it be?

now in \osKitchen\Sources\ROM\Blackstone\OEMXipKernel\
[Windows Mobile Software Development] Ryrzy:
hmm i will try this kitchen but i can't get it work... always:
[Windows Mobile Software Development] burtcom:
OndraSter, thanks -- I got your Kaiser stuff in and have a good 20381 ROM :)
[Windows Mobile Software Development] selyb:
OndraSter: I pray that you can help me with this :(

I cannot get ExtenDir to work. I have completed the same steps now as I did before when I got it to work. The difference now is the version of osKitchen and now I'm using the dissected OEM/EXT that I posted. I hope that it is a bug or something with osKitchen or PRB. I'm still using v1.4 test 8.

I have attached my boot.rgu and I have my whole kitchen here

After flashing my rom, Extendir.dll is in the windows folder and all the registry entries are what they need to be but when I put something in \Extendir\WinDir\ it doesn't show in \Windows\

Extendir is there and everything seems to be configured correctly but it just doesn't work.
[Windows Mobile Software Development] OndraSter:
@zeer

I'll check it when I get home

@ryzy

Do you have properly set up tree structure?

about the tree - I'll screenshot it and post when I get home.

@burtcom

Congrats :).

@selyb

I haven't tried Extendir so I don't really know how to integrate it :o. Sorry
[Windows Mobile Software Development] KilZone:
I only build an ExtenDir enabled ROM once, after which I never really tried again as of the time it took to make it work. However I do remember I had about the same problem as you have now. The DLL is in place and the registry keys are correct, but the change is WinMo doesn't load the DLL as result of incorrect certificates.

To solve this it's easy to include both the dummy certificate (floating around somewhere, I have it but not at my work) and disable the certificate checking. This is normally done by the kitchen (it's an option OndraSter build in) but you might want to enable an OEM yourself (I always leave one enabled with my own security modifications).

P.S. You already know this as you got it working the first time, but as I had the same problem (other kitchen though) once I though I would share my thoughts!
[Windows Mobile Software Development] Tistitus:
Yes, I have everything in it, I think that if I omit something the kitchen wouldn't cook the rom, isn't it?

Maybe the define.txt?

I have:

Native| is true

Is this correct, cos I have in nk a native 6.5 kernel?
[Windows Mobile Software Development] nosedive:
try writing like this

Native|true

wm65_patched|true

wm61_patched|false

...
[Windows Mobile Software Development] Tistitus:
Thanks, I'll try it.

I thought that the correct syntax is as stated in the first page (<folder name>|<is 6.5 true /false> )
[Windows Mobile Software Development] OndraSter:
No, it is just like nosedive wrote - true or false:rolleyes:.

I dug out my original posts about tree structure when I started changing it:

SYS tree

All other trees

And few screenshots:

main kitchen folder

Sources

SYS 23088

ROM Kaiser

ROM Kaiser XIP OEMXIPKernel

NK Kaiser

And there is the MSXIPKernelLtk that works
[Windows Mobile Software Development] bobsbbq:
Ok here is what is strange and may be causing the error with platform rebuilder crashing. The kitchen is not showing all my OEM packages. For Example OEM_Lang_0409 is missing from the kitchen list but as you can see is clearly in the OEM folder.

Any feedback will be great.
[Windows Mobile Software Development] jagan2:
@ivanmmj: np as kilzone said he already sorted that thing for me. Its working great but again in first boot it has some problems and in second boot everything works as it should but after third boot everything returns back to the first boot state.

@kilzone Actually i even didnt touched oem drivers folder. So that rgu is still there plus i even keeped the bluetooth driver bthuart.dll also tried to replace it with gene's, elf's and herald's and added all bluetooth packages required practically it must work with all requirements placed but its not.

Forgot to mention that: i tried that same hybrid package with gene and result was same there also everything was working except bluetooth but when ivan tried on his device it was working (herald).

Will try with all packages and report.

@Ondraster: Hmm seems nice ui will test it and report back but again wats the use when my platformbuilder always crashes:(.

@bobsbbq: May be the prob is same with me too but in mine the whole oem tab is empty :confused:

Edit: I tried the new ui its nice clean and more easy to use. but as bobsbbq said i also noted that oem_lang_0409 is missing could it be a problem for crashing of platformbuilder?

@kilzone i will try to extract oem from other roms via comparing.
[Windows Mobile Software Development] OndraSter:
I think it's the airxtreme's modification for building multiple langs, where it should select right OEM_Lang automatically. I'll look how's it done when I get home.
[Windows Mobile Software Development] airxtreme:
Yes that's normal, I'm having some problems with an aftercheck bug on vista/win7 (http://social.msdn.microsoft.com/Forums/en-US/winforms/thread/9d717ce0-ec6b-4758-a357-6bb55591f956) and I'm waiting to fix it.

Could you please upload the kitchen somewhere (with the save project) and PM me the link so I can take a look at what files aren't correctly moved by the new version?
[Windows Mobile Software Development] bobsbbq:
Well the good news is the extendir.dll seems to now be included even with the old kitchen. Maybe it has been updated as I have not tried it for a while.

So far the one I notice is Only OEM_Lang_0409. I can't upload it now sorry maybe someone else can.
[Windows Mobile Software Development] KilZone:
If the ROM is working on an other device perfectly, wouldn't that suggest that the problem is with your device rather than the ROM you are building? I mean, sure the drivers can be a problem, but the device itself is the most important part. If the BlueTooth part is not working (not your problem, but if) you can use all the OEMs you want but it will never activate.

Alright before I talk too much I think the easiest way to do 'solve' this problem is to download the latest official ROM (this one?) and flash it to your device (make sure it overwrites the radio). Then dump that ROM and take that OEM to start with!

Now build the ROM you build so many times by now but using the OEM you just dumped. This OEM is not yet sorted but that's not a problem (do not use the BT* packages I gave you, since they are from a different OEM). If this ROM has any problems then I ... don't know what ... we'll get to that when the time comes. If the ROM is bug free (as it should) meaning no auto starting Wi-Fi and working BlueTooth. Then we can sort that OEM and use it as a basis (removing the unused files and extracting applications).

This is a problem I have every now and then too, but the problem is always with the packages (usually the modules). What I really like to ask OndraSter how the 'Cooking Log' is build. I believe this not to be realtime, meaning that it will only be shown when PRB reaches 50% and 100% or something? This is not really a problem, but it makes it hard to see on which line PRB crashes. (PRB itself has awfull debugging information, but removing it's output makes it even harder...) Maybe it's just my PC doing this, but if not is it possible to make the output of PRB display realtime?
[Windows Mobile Software Development] OndraSter:
I have a bug when reading prb's output, I know about it and always forget to fix it.

I hope it's fixed now, will post later :).
[Windows Mobile Software Development] OndraSter:
OK so I checked the OEM_Lang and it works this way:

IO.copyDirectory("sources\\OEM\\" + selDevice.SelectedItem.ToString() + "\\" + "OEM_Lang_" + variables["LOCALE"], "build\\OEM\\" + "OEM_Lang_" + variables["LOCALE"]);

it should be copied automatically by Sources\OEM\<device>\OEM_Lang_<locale>

Check your build directory while prb runs...
[Windows Mobile Software Development] jagan2:
Ok, first of all i can confirm that bluetooth part of my device is working perfectly as i can turn on bluetooth and use with official oem and cooked rom (pdaviet one). And also i said it works with other device but i also said that i tested that hybrid oem with gene and herald. And in gene it was same as in opal only in herald it worked. Also i just now flashed another rom from a cheif and it didnt worked either but it seems its like a luck sometimes it works sometimes it wont. So the final solution would be to continue using hybrid oem coz it has only one prob that is bluetooth other than that the whole rom works without any problem. Also the latest official rom for opal is no where in the internet except at one place (i will link u below) the latest one is 1.35.720.2 this one came with indian opal that is mine but i forgot to back up it and now its no where available plus once user from india dumped it and posted the os.nb part only. but i can get oem etc from this os.nb. So atlast if possible can u go through each file of hybrid oem so that we can find out is that linked with someother bluetooth driver i mean the mega one. But also note that if i use oem of any latest phone i get same result although i till now tested the following- mega, topaz official wm 6.5, jade latest.

Ok i think i have made u confused (if u have any q u can ask)

Also the very important thing i forgot to mention you and ivanmmj that with any official opal oem if i cook wm 6.1 or flash the official one it works without any problem this problem only comes when i build for wm 6.5 and 6.5.x.
[Windows Mobile Software Development] twopumpchump:
have you updated your initflashfiles.dat to newer one for 6.5 builds? there are entries for bt in there that arent in 6.1 initflashfiles ;)
[Windows Mobile Software Development] bobsbbq:
This was not my first time just first time with newest kitchen.exe. There is something different as I have tried 2 different builds both build without problem with old .exe. But as soon as I put the new .exe in it errors as soon as it starting Platformrebuilder, and I'm using the same builds that worked with old .exe
[Windows Mobile Software Development] bobsbbq:
You are right it is included in the build log. But there is still some problem with the new .exe as I explained in the post above. Do we need to update the Tools folder?
[Windows Mobile Software Development] OndraSter:
Nah, tools are the same.

Rename platformrebuilder so kitchen crashes, take the build directory and rename it. Now place the old kitchen exe, do the same with it and now compare the old build and the new build, what's the difference please?
[Windows Mobile Software Development] KilZone:
(I know it wasn't your first time, sorry, didn't mean to tell you what the problem was! The 'story' was ment for OndraSter as question...)

I seem to have the same problem as you described indeed. I need to figure out if it's something I did or the EXE only. Right now I'm working, will do some further testing later tonight or tomorrow!

The solution given by TwoPumpChump fits quite perfect actually... since WinMo 6.5 has different modules in there. But do as we talked about before, compare the two ROMs you have with your comparison program and also check initflashfiles.dat (in OEM_LANG_0409) for any changes!
[Windows Mobile Software Development] jagan2:
Thanks for the reply but sorry i dont know what to update could u tell me i have attached my intflashfiles.dat from oem_lang_0409

Hmm i have attached intflashfiles.dat so could u or twopumpchump can tell me what to update.:confused: But i think that by updating i could solve the first prob that is with official oem but when i used hybrid oem i have replaced the whole oem_lang_0409 folder so intflashfile.dat should automatically get updated right. Still if u can point me what to update, i can try.

Yes and i will compare.

Attached intflashfiles.dat

Edit:I got updated intflashfiles.dat from da_g thread wm 6.5.3.3 there its mentioned that it should be updated for device having wm 6.1 kernal. Will try and report back later.
[Windows Mobile Software Development] twopumpchump:
you are missing this entry for bluetooth in your initflashfiles.dat

; BRCM BT shortcut
Directory("\Windows\StartUp"):-File("BTTrayCE.lnk","\Windows\BTTrayCE.lnk")
;remove 1229 Directory("\Windows\Start Menu\Programs"):-File("BTManager.lnk","\Windows\BTManager.lnk")
Directory("\Windows\Start Menu\Programs"):-File("\x0049\x006E\x0074\x0065\x0072\x006E\x0065\x0074\x0020\x0053\x0068\x0061\x0072\x0069\x006E\x0067\x002E\x006C\x006E\x006B", "\Windows\IntShr.lnk")

whenever you edit initflashfiles.dat in notepad and save it, you have to open in hex editor and remove FF FE at beginning of hex or you will have problems ;)
[Windows Mobile Software Development] gathrottle:
Okay I'm Stumped.... No errors from kitchen but extremely small ruu_signed. All files copied to sys, oem and ext but platformrebuilder isn't placing anything in the dump directory, what have I forgot using EVK??

Dave
[Windows Mobile Software Development] airxtreme:
For those who had problems with platformrebuilder try this new build, if it still fails please upload the kitchen somewhere so I can take a look to see what isn't copied or do like OndraSter said, rename platformrebuilder.exe to something else then start the kitchen and when it hangs saying that a file is missing close it and copy the build folder out of the kitchen folder, do the same for the old kitchen and compare the two build folders to find out what is missing.

BTW I also fixed the EXT checkbox issue.

*UPDATE* I posted a newer builds in a newer post with the save problem fixed.
[Windows Mobile Software Development] bobsbbq:
All these below are in the build folder after crash compared with beyond compare.

Ok here are the two main differences I see doing what you suggested above.

1. With the new .exe every packages in the kitchen is included, even those that were not checked. This can cause problems as I have different packages for Tweaks and some other packages which will only work on specific builds.

2. With the new .exe the structure in the ROM folder is different. I will try to give a example.

The following is with new .exe

ROM\

os.nb.payload

romhdr.bin

ROM\XIP\

MSXIPKernel

MSXIPKernelLTK

OEMXIPKernel

ROM\XIP\MSXIPKernel\

23620

ROM\XIP\MSXIPKernel\23620\

busenum.dll

cachefilt.dll

certmod.dll

etc.

etc.

This is with the old working .exe:

ROM\

os.nb.payload

romhdr.bin

ROM\XIP\

MSXIPKernel

MSXIPKernelLTK

OEMXIPKernel

ROM\XIP\MSXIPKernel\

busenum.dll

cachefilt.dll

certmod.dll

etc.

etc.

All others are the same

So it seems that the MSXIPKernel is copying the build number and the contents under the build # instead of MSXIPKernel.

This combined with the inability to select the packages you need may be the problem.
[Windows Mobile Software Development] bobsbbq:
Ok with this build I don't get PRB crash as before. I did notice that I get crashes when trying to save a project.

I know it is early in customization of the new UI but just my opinion, I hate to have to check every single box when you have over 100 packages. And you have to click directly on the box not on the name which makes it even harder.

I would like to see a option where you can select all then go back and uncheck the few you don't want.
[Windows Mobile Software Development] gathrottle:
New oskitchen fixed all issues but does crash when saving a project.

+1 for the select all suggestion.
[Windows Mobile Software Development] rizo83:
lunacie, did you try this? :confused:
[Windows Mobile Software Development] {SBR}_L3GION:
I would love to see this break down the rom and everything like EVK does i like a lot of the feature this thing offers but sadly it is not for my device i would really like to cook with it though great work so far guys keep up the amazing work!
[Windows Mobile Software Development] OndraSter:
bobsbbq: Misplaced MSXIPKernel? Damn, I don't have latest source code, airxtreme must fix it (I overslept and right now I'm going to school :D).
[Windows Mobile Software Development] lunacie:
I did, Raphael works fine. Have not successfully cooked a ROM with this kitchen, yet, though. Problems with htcrt.exe not wanting to run. Could be something in my sys or ext, tho
[Windows Mobile Software Development] lunacie:
+1 on the select all request!
[Windows Mobile Software Development] jagan2:
Wow i think u found out the solution thank you very much iam very much sure now it will work still i will try adding this and deleting FF FE via hex and will report back.:)
[Windows Mobile Software Development] airxtreme:
does this happen also with the build I posted? because those sound like bugs of an early build I already fixed
[Windows Mobile Software Development] airxtreme:
on all pages (OEM/EXT/SYS)?
[Windows Mobile Software Development] airxtreme:
This new version should fix the crash on save.
[Windows Mobile Software Development] gathrottle:
Will have to check tonight, @work right now..... Thanks :)
[Windows Mobile Software Development] totalcmdext:
Problem extraning RUU_signed.nbh

I have the following problem when i am trying to extract LEO 2.02 RUU_signed.nbh rom with the RC3 version:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

System.ComponentModel.Win32Exception: The system cannot find the file specified

at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)

at System.Diagnostics.Process.Start()

at osKitchen.Lib.MyProcess.Start()

at osKitchen.Lib.ExtractRUULib.nbImageTool(String file, String WorkingDirectory, Boolean compatibility)

at osKitchen.ExtractRUU.btnExtract_Click(Object sender, EventArgs e)

at System.Windows.Forms.Control.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ButtonBase.WndProc(Message& m)

at System.Windows.Forms.Button.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************

mscorlib

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.3082 (QFE.050727-3000)

CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

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

osKitchen

Assembly Version: 1.4.0.21

Win32 Version: 1.4.0.21

CodeBase: file:///c:/osKitch/osKitchen.exe

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

System.Windows.Forms

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

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

System

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

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

System.Drawing

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

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

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

For example:

<configuration>

<system.windows.forms jitDebugging="true" />

</configuration>

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.
[Windows Mobile Software Development] OndraSter:
put nbImageTool.exe and xidump.exe in Tools folder, I forgot to post them here. Get them in Dev&Hack.
[Windows Mobile Software Development] totalcmdext:
i have put the nbimageTool.exe and dumpxip.exe in Tools folder in rder to extract LEO 2.02 ROM:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

System.FormatException: Input string was not in a correct format.

at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)

at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)

at osKitchen.ExtractRUU.btnExtract_Click(Object sender, EventArgs e)

at System.Windows.Forms.Control.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ButtonBase.WndProc(Message& m)

at System.Windows.Forms.Button.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************

mscorlib

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.3082 (QFE.050727-3000)

CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

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

osKitchen

Assembly Version: 1.4.0.21

Win32 Version: 1.4.0.21

CodeBase: file:///c:/osKitch/osKitchen.exe

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

System.Windows.Forms

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

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

System

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

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

System.Drawing

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

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

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

For example:

<configuration>

<system.windows.forms jitDebugging="true" />

</configuration>

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.
[Windows Mobile Software Development] janneman22:
Can you add support for the HTC wizard?