How to Cook ROMs using Spocky's Kitchen

Alright Jug6ernaut I had this exact issue too first i was using windows 7 x64 it did this exact problem then i switched to my XP 32 it still did this problem but i noticed one thing. If i ran Erviuskitche.exe through the start.bat option E it gave me this trouble. When i ran erviuskitchen.exe in the kitchen root folder i never got this problem again. I dont know why or how but definately its working for me with that trick see if that helps.

@ eviltuna
i was using windows 7 x64 then i switched to xp 32 and im getting at least some results of course the dreaded issues ur having too but at least its compiling. I have looked all over xda and abroad and the problem might be as Dark described the XIP.bin file it contains important stuff the real question now is how does it get corrupt or why the dumping process corrupts the xip.bin file. Another issue and this is a MAYBE is that the DSM files located in i guess every folder containts a list of the contents of that folder. if we were to say delete monopoly.exe from the sys/oemmisc folder then i suspect that the DSM file still thinks monopoly.exe is there even though it isnt? its just a thought i am sure we are on the brink of success like Dark has managed to do but still gotta find that little issue haha

wow ur exactly right, man i was so close to going insane...thank xD

Alrighty I figure ill go through the tutorial here with everyone so we can see if there was anything we missed its like i memorized it haha.

Anyway
First well need the stock rom which we can get from this website.
Second we need to download the kitchen and extract it anywhere hopefully on an XP 32 bit system as discussed earlier.
Third stick the stock rom .dz file that we acquired into the baserom/gw820
Its at this point we are going to be DUMPING the rom so we launch the Start.bat
we need to select 7 so the dumper recognizes our expo
we will then execute options a, b, c


Thats part C there are some interesting issues that have occurred.
  5.2.21749  5028 Phone_dpi_192_resh_480_resv_800
  5.2.21749  5028 Phone_Lang_0409_DPI_192
  5.2.21749  5028 PhoneRedist_Lang_0409
  5.2.41200  5028 OEMDrivers
  5.2.21749  5028 CommonNonEA
  5.2.41200  5028 OEMMISC
  5.2.41200  5028 OEM_DPI_192
  5.2.41200  5028 OEM_Lang_0409
Different Builds here not sure if they are relevant

[Missing Manifests]
  d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
  723fb954-d931-4348-b672-82a188e587b5.dsm
  161efb55-1b5b-2e9b-a36b-3880a74d745a.dsm
  3346da5d-3675-4a67-925e-75f623184bda.dsm
  b00d0fcf-0459-5ea5-d217-f50a2e1ce607.dsm
Maybe important maybe not

The next steps can be followed using dark's awesome tutorial
the only small note is that in step f the folder the files should be transferred too is the temp/dump/SYS/0409 instead of temp/dump/0409 as there is not 0409 folder in the dump folder.
When all is said and done and assuming we make NO CUSTOMIZATIONS AT ALL just to test out rebuilding process
We continue with step d
dump the xip.bin file
and then we will transfer the wince.nls file. and continue on with the oemxipkernel folder and msxipkernel folder stuff moving them around and so forth
Now at this point DONT press e as it seems me and other people are getting an unhandled exception instead go the root of the kitchen and open erviuskitchen.exe and select the Real WM 6.5 AKU as this tells the rom is an ORIGINAL 6.5 rom because of the increased memory slot capacity that only 6.5 has versus 6.1 very important to have this. Next make sure everything is green in the XIP SYS and OEM the rest is optional packages which we will worry about if we can get it to work first haha
Then the xip build and sys build should be the same number the rom VERSION should be changed based on a recommendation at XDA but i didnt see a difference so thats up for grabs the rom res should be dpi_ so forth and so on
then hit create rom
at this point you should not get any errors at all if running in xp 32 bit also if there is an error  related platformrebuilder.exe that is a simple fix the following line should be added to the kitchen_build_rom.bat
the lines
REM ****************     TOOLS\platformrebuilder.exe
if not "%errorlevel%"=="0" goto error
should be
REM ****************     TOOLS\platformrebuilder.exe
REM ****************    if not "%errorlevel%"=="0" goto error

Boom fixes that issue credits are once again at xda sorry forgot where exactly but it fixed that minor issue.
The next step is simply
f, g, h while naming the rom without spaces
Boom you will have  your "rom" in the buildrom folder in the root of the kitchen. Thats what i did and it seems that im getting some issues with other people. If anyone can add or tell me what im doing wrong that would roxors. not that darks 21901 isnt awesome of course!!!
Credits to most of the info i got from Dark's tut and XDA. The rest is painstaking hours of research haha trying to figure out LG's shenanigans. The log of the dump is attached see if yours matches mine i used the same option a, b , c so we should have the same Right!?!?!??! haha

Question for Dark
     MSXIPKernel from ROM\GW820\XIP. Go to ROM\SHARED and create a folder and name it your build #
     (eg. 23563). Paste MSXIPKernel into that folder. It is important both folders are named the same.
in this part of your tutorial what do you mean both folders must be named the same
also there is already a buildnumber in this folder do we delete that one and create our own?

Here is the part you are referring to:

Now in this step you are only creating 2 folders. When I say it is important both folders are named the same I am referring to the 2 folders you create in this step.

As for the folder already in ROM\SHARED, just delete it. It was an old folder that spocky left in the kitchen from another build.

Awesome, I can confirm it works flawlessly.

if anyone has a gutted oemmisc i would love a copy, mine has the barest of dlls in it to run windows right now hehe.

Hello all,

I have been able to use the kitchen as described here to successfully rebuild the stock ROM (V10g - 21749) and add/remove packages without issue.  However, I've tried multiple times to port a new XIP/SYS build and every time I get the same result: the phone hangs at the orange "Windows" logo screen and won't get past it.

Can anyone point me to what I might be doing wrong?  I've checked for and corrected duplicate packages:
 - The SMS_Providers package was in the OEMDrivers folder from the ROM dump and was a SYS package on the new build, so I tried both disabling the SMS_Providers package and moving the stock one to a SYS package (so there wouldn't be a conflict)
 - The GPSID and Bluetooth (or maybe BTDUN - I don't remember which) conflicted and so I disabled (even removed at one point) those from my new SYS build

I even went as far as to write a small C# program that would analyze the new SYS directory and find ANY and ALL duplicated modules, and they all wound up being in one of the packages mentioned above.

Short of literally copying the SYS packages one at a time from the new build to the old build until I see what breaks (and even that probably won't be a good test since I'd have a "hybrid" SYS folder), I'm completely out of ideas.

My only remaining suspicion at this point (and I don't know how to troubleshoot this) is that there is something wrong with the .ROM or .VM "packages."  My new build only has a .ROM folder, not a .VM folder, and I've tried all combinations: deleting it entirely from the new SYS build as well as copying one and both folders from the dumped 21749 SYS directory, and still no luck.

Any help would be greatly appreciated......  Thank you!