yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] airxtreme:
I'm using wince.NLS as a SYS package so that shouldn't be the problem, I also doubt the problem is with the imageinfo.txt files because platformrebuilder is supposed to ignore them. If you still have both the imported xip and the new xip you created could you please upload them somewhere so I can see if I can spot the differences that could cause the crash? Thanks.
[Windows Mobile] hartv427:
Re

ok np 15 minutes

The one I put toghther

http://www.4shared.com/file/216693318/8913949a/Full_Mine.html

The one from Import

http://www.4shared.com/file/216693004/9bf857a9/Full_From_Import.html
[Windows Mobile] jagan2:
Thank you very much i have started download it will take an hour for me btw is it recmodded?
[Windows Mobile] titan427m:
i keep getting an error when hitting next on the setup wizard: There was no os.nb present in this file! Can't continue!
[Windows Mobile] airxtreme:
Are you using the latest version I released a few hours ago?
[Windows Mobile] agismaniax:
can i use for titan?
[Windows Mobile] titan427m:
The one located on the first page? at this location? that's the one im using

* http://www.mediafire.com/?hku41tcvnim
[Windows Mobile] Tribulattifather:
Awesome!

I have cooked three ROMs so far with this kitchen and I'm getting used to the 'newness' of this kitchen. I really like that I can compress in XPR and then compress each Ext in UPX.

Bravo :)

Cheers,

Trib
[Windows Mobile] titan427m:
i downloaded the kitchen and when i tried to use it, it gave me the error message, so i downloaded the Rhodium WWE and SYSes for 23518, then extracted all the files and inserted them into the source folder (overwriting the old empty ones and still get the same error :(
[Windows Mobile] titan427m:
i want to break things...lol

i cannot get ANY kitchen to work :'(
[Windows Mobile] variosteph:
same errors here

steph
[Windows Mobile] airxtreme:
The three errors (platformrebuilder, imgfstonb, OS.nb missing) are all related to a platformrebuider crash. Please try using one of the already working Sources folder in the first post while I investigate the issue.
[Windows Mobile] hemicalyaction:
Hey. Is there any chance of supporting some older devices (such as HTC Universal, Wizard etc) ?
[Windows Mobile] Tribulattifather:
Hey, are you by any chance cooking for a 96 dpi qvga device? If so, I can help you by giving you my kitchen. It's over a GIG in size, but I'd be able to compress it about 60%..
[Windows Mobile] jagan2:
@airxtreme : After using your sys and xip finally after many months first time i have cooked a rom with os kitchen but u know what it gave me 7 mb nbh :(

Now what may be the problem?
[Windows Mobile] dancer_69:
Building a rom with new UI(version 1.4 RC2.7) for Iolite gives unbootable roms. The device stucks in HTC Mobility screen. Same project builted flashed and booted successfully with old UI(version 1.4 RC4.2).

Any help?
[Windows Mobile] rgb-rgb:
Okay, tried the new version and so far, this is what I had to do.

Using Windows 7 64 Bit

Put Kitchen in C:\Kitchen Folder (I originally had the Kitchen in a download folder but got a Directory access error (Temp directory access) when importing so I moved the Kitchen to the C:\ root)

Before trying to import anything I right clicked on the Kitchen folder and unchecked the box to not allow indexing.

Was able to import the RUU file even though the directory name it was in had a space in it :) Good job on fixing that one.

A couple of things I notice so far:

1)Some of the Packages in the EXT folder have the PACKAGE_Rhoduim in front of the file name. Would be nice to strip this off.

2)Also, all the the packages that have language files, it lists both the package one and the language one with the _0409 (or other language code) added to the end. Would be nice to just hide the Language file and include it by default when the package is selected.

3) All the of EXT packages were excluded from the ROM by default when importing. I had to go through and check each on individually. Maybe include them by default and/or make a check box to Include All/Exclude All.

Tried to Build with and without any of the EXT packages included just to see if it would build and got the Can't run HTC ROM Tool error.
[Windows Mobile] codymamak:
Tried kitchen, no error so far (win7 64Bit - Run as Admin from c:\kitchen solved issues) , but one BIG problem:

If I cook for ENG/USA locale (0409) rom size is about 139MB and seems to be ok , BUT if I cook for my own locale (0410 ITA) rom size became around 7MB and seems useless...

Is there a way to fix this?

BTW I own a X1 (kovsky) and I always use MicroSD method for updates...
[Windows Mobile] airxtreme:
Anybody having problems with import and HTC rom tool, please try running the kitchen in administrator mode.

If you instead are having problems with smaller (7mb) ROM size please post the full log of the kitchen.
[Windows Mobile] jagan2:
Okay airxtreme here is mine i cook for opal and i get exactly 7.16mb output nbh
[Windows Mobile] bobsbbq:
What problem is that? Haven't built with it yet.
[Windows Mobile] bobsbbq:
Well I put all my packages in EVK and I still have the FATFS cache is being set to 0, so there is definitely something changing it. I have tried looking everywhere but can't find it. I tried the WM 7 search in the kitchen but it would not go deep enough in the registry to find even the one in boot.rgu. I have made a provxml but this still bugs me as what else is there included that I don't know about. If anyone know another better way to search for it please let me know.
[Windows Mobile] af974:
Maybe WindowsGrep could help you to find what are you searching http://www.wingrep.com/
[Windows Mobile] bobsbbq:
Thanks I will try. My provxml is not working either? Can someone check it to make sure I did it right. Renamed to .txt for uploading.
[Windows Mobile] af974:
This is mine ...pretty same to yours ...just the 2nd line is inverted .

For some reasons i get 8 mb with it ,but its set for 16...lol
[Windows Mobile] airxtreme:
The solution is in another post wrote yesterday, you have to edit the HTCRT files in Resources\Tools and replace Elf/Touch with Elfin
[Windows Mobile] af974:
Sorry bob, i didnt see it before,lol......here http://xdaforums.com/showpost.php?p=5743618&postcount=12844
[Windows Mobile] hanswurst24:
Putted them in the tools folder and its working now. Thanks!
[Windows Mobile] LokDok:
Still error while extracting ROM

Still error while extracting ROM
[Windows Mobile] airxtreme:
I need a link to the ROM file.
[Windows Mobile] variosteph:
i´m trying to reconstruct the offical 2.07.407.1 rhodium update, sould be 21887 i think...

steph

EDIT:

since yesterday i get the same error like LokDok (Thanks for the picture) but for rhodium

here´s the romlink:

http://rapidshare.com/files/3525929...07.1_Radio_Rhodium_4.49.25.91_Signed_Ship.exe

but i think this must be a problem with my computer, because this error started yesterday after upgrading to 1.17, today i tried 1.16 againe, but the error still exists.

thanks for your hard work.
[Windows Mobile] LokDok:
http://rs356.rapidshare.com/files/3...gned_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
[Windows Mobile] airxtreme:
1.18 is out, please check if it solves the import problem
[Windows Mobile] c2b2:
Error while cooking for Elfin

Just tried out Kitchen 1.18 on my Windows 7 (32 bit). I was trying to cook for Elfin and I got the following error:

ROM Kitchen Executable has stopped working. Windows can check online for solution...

Problem details:

Problem signature:

Problem Event Name:	BEX

Application Name:	platformrebuilder.exe

Application Version:	2.1.0.0

Application Timestamp:	49988ef1

Fault Module Name:	platformrebuilder.exe

Fault Module Version:	2.1.0.0

Fault Module Timestamp:	49988ef1

Exception Offset:	0000d579

Exception Code:	c0000417

Exception Data:	00000000

OS Version:	6.1.7600.2.0.0.256.1

Locale ID:	1033

Additional Information 1:	f0eb

Additional Information 2:	f0eba3f31659c1c46db221701d2f1dea

Additional Information 3:	8cec

Additional Information 4:	8cece402ba7ef5a79360246eedc65efc
[Windows Mobile] airxtreme:
What Elfin ROM file did you import?
[Windows Mobile] c2b2:
I did not get this error while importing a ROM file. I got this while cooking. I'm using builds 28230. I hope this answers your question. (I'm a noob and this is the first time I'm trying to cook a ROM.)

Btw here's the cooking log of the failed attempt:

Cleaning up

Starting a new build process. Actual Locale: 0409

Configuring kitchen to USE:

DPI: 96

ResH: 240

ResV: 320

Device name: Elfin

Native 6.5 Kernel: False

Creating folders

Copying OEMs

Copying SYS

Copying EXT and scanning for all add2* files

Copying other folders needed to run...

Doing UPX on EXT directory

Applying ROM tweaks...

OK, Letting Device-specific preparations...

Deleting unneeded resolutions in Titanium

Running Platformrebuilder

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

Running Tool: Resources\Tools\platformrebuilder.exe

Working Folder: Build

Arguments:

DONE! Now you can flash!
[Windows Mobile] bobsbbq:
I can't believe I have this crazy problem with FATFS cache. I can't get it to change even with a provxml. I have tried to change it by reg in tweaks file, boot.rgu is set to a value of 1000 but after build it is value of 0. I have tried reducing my pagepool to 10.
[Windows Mobile] yonn1981:
airxtreme,

How to include EXEcutor in your kitchen? I want to automate creating .exe ROM for Omnia "i900" ... What I need to change? In ervius kitchen editing kitchen_build_rom.bat do the trick!! I don't see a .bat file in your kitchen so, any feedback?

Thanks....
[Windows Mobile] bobsbbq:
There is no .bat file. Give him the exact name of the file that has to be executed. Also I don't know if you have to set any parameters with the omnia, but if you do he would need these as well. Fo Leo our tool only needs to call the .exe file
[Windows Mobile] yonn1981:
This the line I use:

i900_EXEcutor -a /eeboot.nb0 /iFLASH_%Lang%.bin /ccustomer.csc /fi900_%SYSBUILD%.exe

So I believe is the best way is to call this line within FLASH folder where we can keep the i900_EXEcutor.exe, eboot.nb0, FLASH_%Lang%.bin and customer.csc

:D
[Windows Mobile] variosteph:
no importing problem for me on my work computer, will try tonight on my private computer.

thanks
[Windows Mobile] airxtreme:
I need to know the ROM file you imported to see which file causes the platformrebuilder crash.
[Windows Mobile] bobsbbq:
Well I have bad news for myself it is something in my kitchen. We all hate to have these kind of things where you can't find the issue and it takes a long time to find or you end up rebuilding the kitchen from ground up. I used the EVK to debug the problem because the Temp folder is left after build. In the temp\dump folder the default.hv has the value for FATFS set to 1000, but after cooking it remains at value 0. I used the advanced search utility to completetly search the kitchen and there were only 5 places this exact case match was found "CacheSize"=dword: They were found in Camera EXT packages, My reg tweak file, boot.rgu, os.nb.payload, xip.bin.

I dumped a ship ROM TMOUS 2.10 and only changed the FATFS cache to 1000 and it changed as it should in registry to 4096.

Before I went this far I tried a new fresh XIP unedited from the same TMOUS 2.10 ROM removed Extendir, Changed SYS version and more. So I think it may be in Either OEM or a EXT package.

Either way it means a lot of work for me. BTW no problems with 1.18
[Windows Mobile] bobsbbq:
Also just some feedback on the Uploading.com file hosting service. This site does not like to let me through. Evertime I have to wait 75 seconds then it immediately pops up this error saying time has expired. I go through this 4-5 times and it is really frustrating for a 1.5 mb file. Not sure if others have the same issue or if it is just my location. I attached the screenshot of the error.
[Windows Mobile] javichampi:
There is two ways of flashing Omnia 2, the MST files includes 2 parts: lang.nb and pda.nb, and has a big size because includes all language packs, so it's not very interesting.

The second way is flashing only the pda part with only one language, this is the nb0 archive and it's lighter than mst. You can obtain that part directly from the device, well, you obtain a romdump.bin archive that can be dumped in packages with the program that I linked before. With o2tool you can obtain the pda part too from mst archive but I don't remember how.
[Windows Mobile] Lovetz:
When use build

WMplayer don't work at all. No sound for incoming calls, no sound for alarms, etc. If replace all sys resources with MediaOS from another build, for example 28230 - all works fine.

And one more question - why in every directory in SYS of build 23541 there is file "_skip"?
[Windows Mobile] airxtreme:
I use uploading.com when I can't get mediafire to work, I'll try using depositfiles the next time.
[Windows Mobile] bobsbbq:
The _skip files are used by EVK and platform rebuilder to let the kitchen skip the file.

You will get a better response asking in the Windows Resources thread by Da_G but it is likely some bad or missing modules from the source you got.
[Windows Mobile] airxtreme:
I used o2tool correctly on the MST but the pda.os.nb file it produces can't be used correctly by osnbtool and nbimagetool: when I try to get the imgfs.bin osnbtool returns an error and nbimagetool crashes. Maybe the MST I have is corrupted, can you link one of the latest ROM update?
[Windows Mobile] airxtreme:
Somebody is already releasing 23541 ROMs for the G900 ( http://www.portegeclub.com/forum/viewtopic.php?t=2293&sid=fedeaa007d464046570eaf9c5d051f21 ), you should ask him since I haven't tried using that build yet. Let me know if you find out anything. The _skip files are useless and come from da_g dump.
[Windows Mobile] OndraSter:
I'm not sure if airxtreme did it too, but I implemented _skip files too, that's the actual speedup when cooking instead of copying to temp folder:)
[Windows Mobile] NoName:
why i cook the rom was success, but when i flashed the rom, my phone will stop at omnia logo?

P.S. I cooking the rom for omnia I908
[Windows Mobile] variosteph:
something strange here:

i´m sure i skiped runcc (and it´s not in the log) but the files are cooked in and the rom stoped on the customisationscreen

steph
[Windows Mobile] airxtreme:
I have no idea. Is the i908 identical to the i900? Did you cook an imported ROM or did you use non-stock XIP/SYS/EXT packages to build?
[Windows Mobile] airxtreme:
The kitchen copies the files according to the checked boxes, if the files are in there it means you either disabled the wrong package or the files aren't just in the one you disabled.
[Windows Mobile] wbrown5:
ROM extract error

I actually tried both methods. As for importing the a stock rom, I get an error. I am attaching screen shots of the errors. I am using "HTCTilt2ATTOriginalShipROM" from HTC's website.
[Windows Mobile] airxtreme:
Try the new 1.18 version
[Windows Mobile] ivanmmj:
You can use a batch file to call the kitchen then call your script after the kitchen is closed.

Just checked and you have:

Arguments: -xip "xip.bin" -payload "OS.nb.payload" -PP 6 -imgstart 0 -nocert

For the Opal.

Remove the imgstart and nocert on it. (Well, I'm not 100% sure about the nocert, but definitively the imgstart. It doesn't like any of that to be moved.
[Windows Mobile] LokDok:
I dump my Topaz original rom

chek all packages SYS OEM EXT

no tweak

after cooking and flash my Topaz stoped on the customisationscreen

sorry my bad English:(
[Windows Mobile] airxtreme:
1.19 is out with batch file support
[Windows Mobile] Rataplan:
Okay, after flashing several rom's, (cooked with V1.16) all the rom's stopped at the custimosationscreen, but after a softreset the rom's passed the custimosationscreen and I can customize my screen, everything works normal, no issue's at all, just hoping someone can point me through the right direction to solve this small issue.

I cooked the rom's for the Niki 100 in the Dutch language.

Regards

Ok, same issue with V1.19 so it must be something what I am doing wrong, so any help would be appreciated.
[Windows Mobile] javichampi:
Omnia II

http://www.modaco.com/content/i8000...on/293492/secanys-i8000-wm65-rom-feb-10-roms/

At the end of first post is the latest version. I have my own romdump.bin file, and some cooked ROM's links in nb0 format if you need it.

The wes58's kitchen uses osnbtool too, so maybe you're right and your pda.os.nb is corrupted.

Thanks for your efforts.
[Windows Mobile] bobsbbq:
Just to let everyone who cares know, I found and fixed my problem with the FATFS cache setting. It was in my reg tweak file. I had changed some settings for Disable power management on several different things and I guess it had something to do with that. When I changed them back all was working again.
[Windows Mobile] bobsbbq:
Can someone explain to me how the 1.19 batch file works? I can't find one in the new kitchen.
[Windows Mobile] c2b2:
My initial problem about platformrebuilder seems to have gone after installing 1.18 (I'm cooking for Elfin and my OS is Windows 7 32 bit).

But I get an error while building. I'm using RUU_Elfin_DOPOD_AU_2.20.710.2B_4.1.13.51_03.07.90_BLUE_Ship as the base ROM during initial importing and using the 28230 builds. I am posting my cooking log here. Can someone please tell me what I'm doing wrong. Thanx a ton.
[Windows Mobile] af974:
Open Oskitchen and check tweaks tab......do you see the last voice?
[Windows Mobile] af974:
You got the answer from Oskitchen...check OEMdrivers to see if you have 2 or more .rgu files.

Rgu is the extension.

EDIT: if you have extracted an RUU_signed and also did you download the source device from first post , you maybe have to oemdrivers folders
[Windows Mobile] bobsbbq:
Ok I see it now. Never mind I copied some lines from the EVK and got a batch file to work now.
[Windows Mobile] af974:
You only need to select the LeoCustomRuu.exe, though i do this for kaiser and it start flashing after end the build process.
[Windows Mobile] bobsbbq:
Well the problem with cache is back, I thought I had it fixed.
[Windows Mobile] af974:
Its strange...but with OsKitchen v1.19 ,now also os.nb wont be deleted after end building ......i guess im the only one to have this issue,any advice ?
[Windows Mobile] bobsbbq:
It seems that if you don't have a application selected to run after build nbh it doesn't delete the os.nb. But if I select a app from the tweaks tab to run after build it deletes it.
[Windows Mobile] af974:
Uhmmm...thats strange because i had selected them.
[Windows Mobile] bobsbbq:
EDIT: Now after I closed my kitchen and reopened it mine is not deleting anymore as well. So no you are not alone.

BTW I really found the cache problem this time. It was a registry setting in a cab a made a long time ago with several apps packaged together like soft reset PPCPIM etc. And that's why I could not find it in the search. Got it now though and my performance is a lot better as it was also setting my Glyphcache to 0 as well
[Windows Mobile] yorick_wei:
any other mirror?i can not download from mediafire.tks!
[Windows Mobile] c2b2:
I checked my OEMDrivers folder. There's no .rgu file. That was the 1st thing I'd done when I'd seen the error.

Also, after installing the kitchen, on the first run, I extracted a ROM as mentioned in my previous post. And then I copied sources from the 1st post.

The part of your quote which I've highlighted is not very clear. Can you tell me again what do I need to do to the OEMdrivers folder. Thanx.
[Windows Mobile] af974:
Yes sorry i wrote bad ........i meant " you maybe have 2 OEMdrivers folders.

Its impossible to dont have an RGU extension file in Oem drivers,there are many system reg inside.

Check your windows folders setting ,you need to letting windows see hidden and system files otherwise you will not see the RGU file.

BTW is a file like " fbfg333kkdhjedasa.RGU
[Windows Mobile] indresh88:
opal

Not working for opal,

when i flash the image in my device,after 100% done in ruu the message comes,

"upgrade rom error" and device go into bootloader mode

what would be the cause?
[Windows Mobile] c2b2:
Yes. I had 2 OEMDrivers folders. I dont know how. I deleted everyting and setup a fresh install. Then I copied the sources from the 1st post. After that, I run the Kitchen. This time it didn't ask for importing a ROM file (as it always does on first run). So I didnt import any ROM and cooked a basic ROM. It worked flawlessly :D

I haven't tested it yet. But I'm happy I went at least thus far. Thanx for the help.
[Windows Mobile] airxtreme:
That is a different issue, it is certainly some module your are trying to cook that is causing crashes.
[Windows Mobile] indresh88:
i have been got that solved.....but the new problem is once i flashed the nbh image my device go into bootlOader and it says "upgrade rom error"
[Windows Mobile] airxtreme:
What was the module causing the crash? I know about the bootloader message, I did some changes in the kitchen maybe the ROMs for Opal are going to work in the next version out today.
[Windows Mobile] indresh88:
this only occur with 23541 sys and i found that,

it was the .dsm file missing in MSXIPKernel>buildname(23514) folder ............try to add .dsm file from other build...........

by the way when you are going to release next build..........for opal:)
[Windows Mobile] Rob_Storm:
Any chance of support for Samsung i920 (Omnia II CDMA)?
[Windows Mobile] bobsbbq:
According to this MS article the FATFS CacheSize setting is obsolete.

http://msdn.microsoft.com/en-us/library/aa914334.aspx

Disregard, It must still be used even though it says obsolete because changing it to DateCacheSize made performance really slow.
[Windows Mobile] c2b2:
Can't make a ROM that works :(

I imported an original ROM, built it as is, and flashed it. It worked.

But then I added new builds 28230 in MSXIPkernel and SYS. Then when I select these builds and cook, the ROM I get doesnt make my phone boot when flashed.

Can someone please guide me. Thanx.

(Btw I am trying to cook for Elfin)
[Windows Mobile] af974:
Be sure to use ,in Common, only files not modules and also check if Oskitchen is recmodding your SYS modules.

Try to leave some big packages like Office,Wlive,messenger and see if it boot.
[Windows Mobile] airxtreme:
I did some changes to the htcrt project generation so I'm waiting to test the changes properly to make sure the sections aren't mixed up, it'll take a while because building a rom takes more than 15 minutes on my slow pc :(
[Windows Mobile] ivanmmj:
You can't just use EVERY package in the SYS on most devices and expect it to work, unfortunately.

Airxtreme, did you see my post about the possible Opal issue? I think those changes would fix the problem.
[Windows Mobile] indresh88:
something might be wrong h...because the same sys,msxip i use in earvius visual kitchen get boot.....
[Windows Mobile] airxtreme:
Yes, there's something wrong in the ROM file generation. The next version has some changes to support Opal but I'm not sure if it's going to work yet. If 1.20 still doesn't work please point me to the latest Opal ROM and also the ervius cmd file for Opal: those could help me fixing the problem.
[Windows Mobile] c2b2:
I selected almost all the packages. I left out the the East Asian or Arabic ones and also I selected files and not modules wherever applicable.

Still no progress (the ROM gets cooked, but does not work on the phone).

After the smart mobility screen, the screen goes black and stays that way :(

Also, I don't know what is recmodding or how to check if the OSKitchen is doing it.
[Windows Mobile] af974:
After ending process ,select the log of build and press Ctrl and c ,then paste it in a blank note and post it here.
[Windows Mobile] c2b2:
Here's the log:

Thanx for being so helpful.