yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] airxtreme:
I think I'll just add a menu entry to load packages from another device as soon as I can get rid of platformrebuilder that is crippling the folder structure.

I'm pretty sure the packages don't cause any trouble or it would have been reported before since those have been recmodded by default for months. Your problem seems to be provxml-related, please try the latest beta4 on a clean ROM import to see if you still get the same issues.

I added a imgfs free space setting in the latest beta4. I can also add an option to copy back the DSM files but you'll have to check first if it works since imageupdate could also rely on packages.sof/cif that need to be updated to reflect the new packages tructure.

I tried on an HD2 rom and everything seems to be fine
[Windows Mobile] crane23:
no advanced tweaks

v1.31beta4 no advanced tweaks?
[Windows Mobile] Staxxthedan:
From a dumped ROM bearing the same Manilla Version you want to update to.:)
[Windows Mobile] zxb11925:
Language file can used in beta4

Hi airxtreme,

The same Chinese language file which can't used in beta3 is now can used in beta4!
[Windows Mobile] zxb11925:
Use CFC compress can't start the device

Hi airxtreme,

My device is HD2, I used CFC compress with manila 2016, but it is failed at first screen?
[Windows Mobile] makeveral:
hi airxtreme!

Just updated my kitchen to beta 4 and cfc compression didnt work well (corrupted graphic files/invisible etc) with beta 3 it was ok.

I dont know if the problem is because i updated the kitchen to this new ver. or if it's an error of beta 4. I'm gonna put the original manila packages again and see what happens.

regards
[Windows Mobile] Diegis0n:
1.31beta(x) / 1.30v3 - splash issue?

Hey airxtreme :)

Im must say since the Zero series your kitchen is growing fast !! Great work :cool:

About the splash image: i select it but it doesn't get cooked in?

Pre 1.25 works good though.

EDIT

I overlooked this here:

All good now :D
[Windows Mobile] airxtreme:
Please try clearing the Resources\Cache folder of the kitchen since I may have changed the file dates between the versions
[Windows Mobile] airxtreme:
Did it work with beta3?
[Windows Mobile] joshkoss:
I have HD2 and on both beta 4 and 5 CFC Compressed option and they work great!
[Windows Mobile] zxb11925:
It didn't work from beta3 to beta5
[Windows Mobile] birkoffsjunk:
I've found beta5 to stop during the "Generating IMGFS file from DUMP" stage (not crash as such, application is still responsive), rolled back to beta4 and ran it again built ROM successfully. Only change was beta4 <> beta5 exe.
[Windows Mobile] airxtreme:
Did you replace the Resources folder with the new one included in the archive? There is a new imgfsfromdump version in there.
[Windows Mobile] airxtreme:
Did you try deleting the Resources\Cache folder? I changed some stuff in there since beta2
[Windows Mobile] birkoffsjunk:
I have, but I'll double check ;)

EDIT: I definitely have the updated IMGFSfromdump app. Here is the MD5 just in case, 82FB32BE6AB0E4F1A4D8142DF2D7BDC2
[Windows Mobile] freemanxp:
When I dump a nbh from RUU_Leo_hTC_Asia_WWE_1.66.707.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship, the oskitchen works well,

but when I dump a nbh from

RUU_Leo_1_5_hTC_Asia_TW_2.14.709.P1_Radio_15.39.50.07U_2.10.50.26_Signed_LEO_Test or any other newer rom , it shows me an error below at the beginning

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

Error while importing the ROM file

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

Error while importing the ROM File: Unable to dump the NBH file: Unknown internal DLL error

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

OK

---------------------------,

but if I use nbImageTool.exe to dump the nbh manually,there is no problem,

:omay anyone please tell me what's problem is?
[Windows Mobile] zxb11925:
I have deleted the Cache folder.
[Windows Mobile] airxtreme:
If it crashes it most likely means that it's corrupted, try extracting the ROM from the official EXE update. I imported "RUU_Leo_1_5_hTC_Asia_TW_2.14.709.P1_Radio_15.39.50.07U_2.10.50.26_Signed_LEO_Test.exe" downloaded from here and everything went fine. Try the ROM I linked and if it still crashes make sure you don't have anything locking the file like antivirus or firewalls.
[Windows Mobile] zxb11925:
Now, It can start fine, but the images can't diaplay?
[Windows Mobile] Diegis0n:
It did this for me as well (beta3) a few times, not once on 4, will check 5 out soon :)

weird huh
[Windows Mobile] birkoffsjunk:
You know what I think it might have been the manila cache... just deleted it there, replaced exe with beta5, and it's now running perfectly
[Windows Mobile] Diegis0n:
Makes me think about another weird behaviour i forgot to comment about on beta3:

I cook multilang obviously. One of my project files cooks 11 langs in a row right?

Well, at one point it would cook the first 7 and crash every time on the last 4 with some error i can't remember :p many retries got the same result: 0414, 0419, 0816 and 041D would not cook ... tried them one by one etc no joy.

What fixed it for me back then was to extract a fresh osk1.31beta3 zip and replacing the old exe and Resources folder iirc.

No idea what went wrong there :eek:

PS: beta5 is all good! didn't try cfc manila option coz my manila is already cfc'd so i can't comment on that ^^
[Windows Mobile] freemanxp:
Thank you very much for you replay,downloading and I'll try it.
[Windows Mobile] KilZone:
I recently upgraded to the new kitchen version (came from 1.18) and I seem to have the same problem, no matter what version I use (1.30v3 and up). If I select 'Compression: NONE', the ImgfsFromDump starts, but then just remains idle all the time. If I kill it the kitchen perfectly reports that it has failed in building the ROM.

When I select XPR or LZX compression the process is complete and the ROM seems to work great. However my device (BlackStone) has enough ROM and RAM and thus I prefer not to use any compression.

@AirXtreme The changes are great, but I have a question. You recently implemented a warning dialog when you not include an essential package and start creating a ROM. I think for most users this is a good reminder, but I do not include 'FWUPDATE' and 'SQM' on purpose (performance reasons) and now am reminded of this every time I hit 'Start building' (even though I did include the dummy versions). Can you create an option to suppress those warnings (no real need to make it special for these packages, an option to suppress all SYS warnings on 'Start building' is good too)?
[Windows Mobile] + Que PPC:
Or alows Kitchen to check if we have the EXT or OEM dummy PKGS for SQM and FWUPDATE... this way you can not have the original but dummy, and the reminder dialog pop up wont shows... maybe we need the PKGS in a special format (OEM OR EXT) or a fodler with a special name to be detected ;)
[Windows Mobile] OndraSter:
or check for cutstat.dll and the other one from fwupdate :)
[Windows Mobile] airxtreme:
Please try the imgfsfromdump I attached: I think there was a sharing violation that could have caused trouble on fast PCs.

Are you sure the packages are named "Dummy SQM" and "Dummy FWUPDATE"? The kitchen should already manage alternative packages.
[Windows Mobile] KilZone:
That new ImgfsFromDump works perfectly fine, just flashed the first new ROM and works awesome! Thanks!

I did some testing regarding the SQM and FWUPDATE. First, I did name the packages Dummy_SQM and Dummy_FWUPDATE instead of using a ' ' blank space, but renamingthem alone was not enough. The reason it kept complaining was that I placed the dummy packages in my EXT as I do not need to have different dummy packages for every single build. If I place them in my SYS it works as you said, it recognizes the package as dummy and does not show the warning.

But I now have 8 different WinMo builds in my kitchen (mostly for testing purposes) and use the same dummies for all of them. Is it possible to implement the same feature you have for SYS also for EXT? This way we can use only one dummy package for all WinMo builds, instead of having to copy them to each SYS.
[Windows Mobile] Omega Kaos:
Hi,

Does anyone know if the new beta 5 version cfc compresses ext packages like GTX Theme or do i need to do that seperatly

Many Thanx
[Windows Mobile] toadlife:
Running the latest BETA(5) and it's working great. Thanks for including the "disable kernel cleanup option".

I've read anecdotal reports that extreloc does a better job than platformrebuilder at handling modules. I found an old-style kitchen made for the Omnia that used extreloc and coverted it over for the rhodium. I've found that when using extreloc, modules (e.g NotificationEnhancement)) that have to be recmodded with platformrebuilder work fine with extreloc.

The big problem I've had with the old-style extreloc kitchen that I made is that the rgu files are not processed in the correct order by BuildOS. Using batch file, I can replicate everything that BuildOS does except rebuilding the packages.sof, so I'm stuck with BuildOS and ROMs that exhibit rather strange behavior.

Could this kitchen be converted to use extreloc?

Edit: Removed the part where I said I saw extreloc was in the OSKitchen tools folder. I was mistaken.
[Windows Mobile] KilZone:
I might be doing something wrong, but the add2* support seems to be broken. No matter what I try, no code is added to 'config.txt' or whatever add2* I use. Anyone else having the same problem? Or am I doing something wrong?

I've placed the add2 file where I normally did, in the root of the EXT package next to the app.reg file. I used to work...

edit: Placing the add2* file inside files folder of the EXT package only results in the file being included in the ROM but no lines are added to the config what soever.

edit 2: My mistake, I checked the wrong file! The kitchen is doing its job fine, I just checked the original file (copied one though) instead of the real included one! Sorry all!
[Windows Mobile] tidus18:
+1. Me too, i place my dummy packages under EXT, so i get warning on each build attempt. I try not to modify any files in SYS, so i copy the required files to EXT packages and modify them. So, it should overwrite the files in SYS during build process.

Great job airxtreme! Thanks.
[Windows Mobile] jjblaster3:
as long as u have enabled cfc compression it will check all ext packages if manila graphics files are available, and then works on compressing them so no matter what manila theme/graphics customization u add it will be compressed

sorry for the late reply, had internet probs the past week so wasnt able to download the update, just wanted to let you know that it works fine now in beta5(skipped beta4), THANKS :)
[Windows Mobile] Kalip:
I have a problem with this kitchen.

I have extracted all and have the right folder structure.

After trying to start oskitchen.exe, i'm getting the following error message.

Beschreibung:

Stopped working

Problemsignatur:

Problemereignisname:	CLR20r3

Problemsignatur 01:	oskitchen.exe

Problemsignatur 02:	1.0.0.0

Problemsignatur 03:	4c376d67

Problemsignatur 04:	System.Xml

Problemsignatur 05:	2.0.0.0

Problemsignatur 06:	4a275e0f

Problemsignatur 07:	210a

Problemsignatur 08:	224

Problemsignatur 09:	System.InvalidOperationException

Betriebsystemversion:	6.1.7600.2.0.0.256.1

Gebietsschema-ID:	1031

Running Win7 64bit, i have .NET 3.5 (updated today to 4.0), Visual C++ 2008 Redist x64, MSXML 4.0.

Was searching the whole forum, but no luck finding anything related to it.

Anyone know whats the problem ?
[Windows Mobile] kurniawan77:
wow... i'm still on beta3....hehe working fine for me!

Do i need to redump everything on beta6??? :(
[Windows Mobile] KilZone:
Just overwriting the osKitchen.exe and the Resources folder will do the trick, the kitchen structure is the same. You might want to move the 'Dummy SQM' and 'Dummy FWUPDATE' to your EXT, as it saves a little disk space (couple of MB).
[Windows Mobile] kurniawan77:
Thanks for the tip Kil...

Do u want to share those packages???
[Windows Mobile] KilZone:
I couldn't recreate the exact same problem, but the symptoms suggest your 'Resources' folder is incomplete. Try to re-extract everything from the archive, and not to create the folder structure yourself.

Just do the following:

Download RAR

Extract to Location

Execute osKitchen (make sure you run it as 'Administrator')

Import ROM

If this is still not working, you will have to wait for AirXtreme to see if he can recreate the problem (he is the real master here, I just know how to use the kitchen...).
[Windows Mobile] KilZone:
Sure, here they are: View attachment 359598

These files will replace SQM and FWUPDATE in the SYS, so make sure that you disable those packages from SYS (both dummies are smaller, contain only the required files, where the originals are larger). I included the registry settings I use for both packages, so should be plug-n-play...

@NIKOSXRI Those packages are OEM packages rather than EXT. They work great, but for use in the EXT of this kitchen they need to be altered slightly (like the packages in the download above). [And there is no reason to be sorry!]
[Windows Mobile] NIKOSXRI:
here you are
[Windows Mobile] kurniawan77:
you guys r fast!!!! thanks a million!!!!!

edit: running perfect kilzone... still on beta3 btw...
[Windows Mobile] airxtreme:
EXTReloc may be compatible with more modules but it's hard to automate (the window won't stay shut) and requires XIPPort that is a very nasty tool. Da_G is going to write relocation in his library and as soon as he's done I already wrote an internal build system that does everything platformrebuilder does without all the file copying to build ROMs with it. The only concerns with platformrebuilder are speed and compatibility because usually when platformrebuilder works even if slow it does the job very well however getting rid of platformrebuilder would allow me to could cut the building time from minutes to seconds because I probably won't even have to copy a single file but just feed a list to imgfsfromdump (and if I added a compression cache to imgfsfromdump the building would be almost instant because most of the files won't have to be compressed again).

You have a problem with XML libraries (not MSXML 4.0 but the ones .NET uses) but I have no idea what it is about: it could be a corrupted Windows install or an antivirus messing with the XML library but it's a problem that is only happening on your machine since nobody reported it before and I tested the kitchen on clean windows installs.
[Windows Mobile] toadlife:
Thanks.

I know what you mean regarding automating extreloc and xipport.
[Windows Mobile] coolsac32:
the kitchen keeps crashing when i wanted to cook in a .zip file
[Windows Mobile] Kalip:
Thanks for the Info.

Yes, it's my machine. I testet it yesterday evening on my brothers machine and it was working. Hmm, i need to investigate then.

AntiVirus shouldnt be a problem, we both have the same with identical settings.

Maybe you have an idea where i have to look to fix it ? Re-Install of Win7 is the very last option, because i have so much stuff on it.
[Windows Mobile] KilZone:
Try re-installing the .Net Fx 4.0. You can do this by either going to the 'Repair' option in the Control Panel and then Software or by downloading the installer again. I think that if it is the .Net Fx, this is the most likely option to fix your problem!
[Windows Mobile] tidus18:
Bravo!

@airxtreme

Bravo! Your latest release seems no longer gives me prob with manila management. In previous builds with my kitchen setup, it would go into "Idling" when it hits Digital Compass with CFC compression enabled. I tried deleting dsms, removing my custom packages, etc and couldn't get it to work previously.

Thanks airxtreme! Your kitchen is getting better day by day and cooking rom never been easier! :):):D
[Windows Mobile] pongskie:
Hello guys! i'm really new about cooking roms but i'm willing to learn to be best that i can. Today i tried using this osKitchen, i loaded the stock rom:_HTC HD2_RUU_Leo_HTC_ARA_1.66.415.3_Radio_Signed_15.30.50.07U_2.06.51.07_Ship

and i loaded the build: 23569_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409

then i remove some useless things in the sys packages,

then i hit the start building button..

but i'm afraid of flashing the output rom.. my hspl was 1.42, the current settings of my phone are in my sig.. please advise anyone..

Thanks and Regards,

Pongskie
[Windows Mobile] NilsP:
@airxtreme

Since you get a lot of "I am having problems" posts I thought I would post a positive experience.

Background: I have not had any luck with the 1.31 betas however, 1.30v3 was working perfectly. Kitchen would load and create a ROM but it would not boot.

Today: Installed 1.31beta6 and it is working flawlessly. Seems to run faster and the ROM is working perfectly.

By the way, this is on a DC22 i910 Omnia with 23569, 28236 and 23123
[Windows Mobile] lukapa8:
Avsome!!!! Great works!!!!
[Windows Mobile] Kalip:
Yes, i did. Also, i tried the Net Framework Cleaner. No luck.

Anything else i can do ?
[Windows Mobile] Nokser:
Maybe create support for Samsung I600 :cool:
[Windows Mobile] airxtreme:
Please link the verizon ROM you imported, maybe that'll help me fix that for the next kitchen version.
[Windows Mobile] airxtreme:
Are the ROM files for the i600 just like the i900 roms?
[Windows Mobile] Nokser:
I tried, but not the structure for the system, I have the same problem as in your kitchen with the E72
[Windows Mobile] airxtreme:
Then there isn't much I can do to help until prb adds support for those devices.

BTW the prb issues are with the XIP right? have you tried recmodding and reversemodding all the XIP files to see if maybe prb stops having problems?
[Windows Mobile] Nokser:
In truth, to put platformbuilder

Did he ever work with smartphone?
[Windows Mobile] icon123:
Thanks. I just tried rebuilding the vzw Rhodium rom with this kitchen and it still doesn't get past the first boot screen.

Here's the link, just click on the mr1 update on the right:

http://www.pcdphones.com/phone_downloads.aspx?bid=128&cid=1&mid=356&carrier=Verizon Wireless
[Windows Mobile] airxtreme:
I never tried but I think it should work fine.
[Windows Mobile] af974:
Great Job airxtreme!!

LOL...every day a new version....:D ...you need some rest
[Windows Mobile] Nokser:
In this issue, it does not work ....
[Windows Mobile] hartv427:
Have you tried cooking and flashing the origonal sys form the mr1 upgrade before trying to upgrade the sys ? If not start with that first. I imported built and flashed that rom with V1.07 at least three times last night without fail and I'm typing this with my device now
[Windows Mobile] bobsbbq:
New kitchen 1.08 works good and very fast. I really love this kitchen. Airxtreme any ETA on the add2config.txt fix? Also the details for the Device LEO are wrong I put the correct ones in my previous post.

Thanks again.
[Windows Mobile] Nokser:
How to this kitchen, rebuild package SYS ?
[Windows Mobile] icon123:
Thanks again for the reply. That's what I tried last and same problem. However, I may of had a problem importing the nbh into the kitchen. I'm trying again from scratch.
[Windows Mobile] hartv427:
That should work for you. Then make changes slow
[Windows Mobile] jeng28:
Nice GUI.

Is it possible to cook rom for O2 Stealth? I would like to get Android work on this device.

Thank you.
[Windows Mobile] icon123:
Unfortunately, it did the same thing. What could be going wrong? I think we are using/doing the same thing. I import the mr1 update into the kitchen. Pick all oem, sys, ext and cook. What else could I be doing wrong. I get no errors, just won't go past the boot sceen. BTW, I did get this working with EK.
[Windows Mobile] hartv427:
try this

http://xdaforums.com/showpost.php?p=5583197&postcount=155
[Windows Mobile] bobsbbq:
Another feature Request to put in the back of your mind. Is it possible to place a button on the top right to initiate the Flash ROM function? It would just make it easier if you are going to flash right after building.
[Windows Mobile] icon123:
Thanks, I'll try that. What type of compression you guys using? Does it matter? Normally, I don't use compression but with this kitchen, it seems like you have to.
[Windows Mobile] KilZone:
Using todays tools you almost cannot 'kill' your device *, but the ROM you build can be flawed. However, if you have (as you said) HSPL that should not be a problem.

Todays tools have various safeguards in place, so you cannot flash harmfull ROMs to your device. The first thing you will notice is that if your ROM is not specifically made for your device, the flashing procedure will abort. If your flash is complete, the ROM itself was good, but that doesn't mean that it is correct. After flashing, the device will reboot and start the 'installation' procedure (cold boot) and might hang there. There are two ways your device can hang. The first is when your boot loader (spl) will not load the ROM, you will be stuck on the screen with boot loader information. The second is when the installation of Windows Mobile is finished, if there is a problem during the install it will produce a full white screen. Both these problems can not be solved without a reflash, so as long as you have not build your own 'correct' ROM yet, it is best to keep your current ROM around. Last, but not least, there are several lockups your device can experience, but those are most of the time easier to fix. These happen during opening of a certain application or file, but can be solved by 'soft resetting' the device.

Easiest way to create your own ROM is to start by (as you did) dumping the original ROM and just recook this one. Then slowly replace applications by their newer counterparts (do not do this all at once, as you will then not know what causes the problem, I usually do it per sets of 3 or 4).

* Flashing many ROMs always has some risk involved, but that you already knew as you do not run the original ROM anymore.
[Windows Mobile] KilZone:
You can try to run the kitchen in compatibility mode for Windows XP (Service Pack 3), this should force the kitchen to use a slightly different version of the .Net Fx (which might be working).

Also make sure it is ran as 'Administrator' (I think the kitchen does that automatically, but not sure).

Where have you stored your .exe? Best is to place it in your personal folder (where downloads, documents, etc. are) and to run the .exe directly.
[Windows Mobile] kurniawan77:
updated to beta7 from beta3 gave me troubles...

(i only replaced the .exe and resources folder).

Startmenu is again not builded wel... like some icons not moved to a certain folder like Outlook, Messaging, Tools.... And these folders are not having those nice icons we see in Project Default A. Another thing is that the time is not being set in Oobe... i think it goes wrong at some .provxml files...

I didn't had these faults on beta3 so i'm heading back. Maybe i have to redump everything again in beta7??... but not today... unless someone has a better idea...

Regards kurniawan77
[Windows Mobile] KilZone:
I had the exact same problem once too, but as far as I know it has nothing to do with the kitchen you use. The problem you're having is that the 'mxipupdate_projectdefault_a_000.provxml' is executed before all the other provxml are completed. (Most likely you have a mxipupdate_* which starts with a letter later than 'p'.) This way not all shortcuts are set (some HTC applications place their icon in the start menu on cold boot) and thus if you try to move an icon which is not there, the provxml execution fails. Windows Mobile does not provide any error reporting for provxmls and just halts all execution after an error has occured.

This kitchen allows you to set priority over other packages, but I'm not sure if these are reset on upgrading your kitchen. So make sure that all packages have priority over ProjectDefault_A.

Another thing you can do is rename the 'mxipupdate_projectdefault_a_000.provxml' to 'mxipupdate_zprojectdefault_a_000.provxml'. This way you force Windows Mobile to execute this file last, as it will execute in alphabetical order, unless forced otherwise. I use these kind of provxml in my kitchen all the time, 'z' for late execution, 'zz' for very late execution and 'zzz' if have no more 'late' options left.