yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] FLOKER:
[WM Kitchen] OsKitchen Zero v1.31 - The easiest visual kitchen

Hello,

I tried so many ways and I don't know what to do anymore.

Here's what I'd like to do and what I did already:

I chose osKitchen for developement and imported the Gen.Y Kitchen for the Diamond. It's WM 6.1 21056 Build with actually a few mods and so on. Now I would like to import a new 6.5.X build. I downloaded this one, because I also need german languagefiles. Everything should be in there if I'm right. Then I imported the build into the kitchen - did nothing further, just chose it on the Project Settings Tab and run the building routine.

Now my phone comes till the Screen with the red-orange background and the Windows-Mobile logo.

Could anybody help me or provide a quick tutorial, what to do to import 6.5.X 23563 into a working 6.1 osKitchen?

Thanks in advance
[Windows Mobile] af974:
Ok......now that you are in the right thread lets see how to solve your problems.

Did you recmodded the Oskitchen suggested EXT packages?

Most important is Notification Enhancement

then Concurrence MGR.

If you have a 6.1 Kernel you need to recmod also some SYS packages........im not sure but if im not wrong there are some Diamond 6.5 kernel around.
[Windows Mobile] vasujahagirdar:
platform builder crashes

hi friends,

im new to kitchen section,using custom roms in my poor elfin .now tried to cook my own roms with Oskitchen zero v 1.31,for which i setup kitchen with stock rom 6.1 of my elfin.and imported 23563 rollup/23686/23688 builds ,but when i start to build the platform builder gets crashed all the times saying some unsupported modules present in the packages which has to be corrected(which ones i dont know ofcourse)i imported mega manila packages ,whether i select them or not same result.plz help me what wrong i am doing.when i tried kitchen v1.32 alfa7 ther will be X mark IN MSxipkarnel in sys packages(saying more rgu files present),also X mark in OEMdriver in OEM ( Saying many files having incorrect dword values ) though rom is built with stock rom .

help me
[Windows Mobile] ADB100:
Probably a dumb question - Manila?

After a bit of playing around I am at least now getting working 6.5 ROMs on my new (eBay..) Blackstone.

I have done the following:

I have imported the latest European WWE ROM (RUU_BlackStone_HTC_Europe_1.56.401.0_Radio_52.62.25.34_1.13.25.24_Ship.exe) - saying yes to the initial recommended RECMOD

Replaced the 6.1 Kernel with the 6.5 Kernel I found on here (Blackstone-WM6.5-OEMXIPKernel.zip) - Replaced the OEMXipKernel folder in \profiles\default

Imported a new Windows Mobile Build (23688)

Added various applications I want included in the ROM

Built the ROM & Flashed it

I want to include a later Manila build but can't seem to find a package that will work - The one included with the Stock ROM is 'Manila v1.3.37395.2' and I'd like v2.5x. If I exclude this and include (what I think is?) a later Manila build then PlatformRebuilder.exe crashes.

I have searched on here and on Google and have found various files to download but I am missing some (obvious?) piece of information to get this to work.

Andy
[Windows Mobile] airxtreme:
Were the ROMs working before you switched to the new windows mobile build?
[Windows Mobile] airxtreme:
It's probably just a duplicate module but if you upload the kitchen folder somewhere I can take a look and tell you the cause.
[Windows Mobile] airxtreme:
Try using 1.32 and check if the new manila comes with any module that is also present in OEMDrivers/OEMDriversHigh (the OEM ones have to be deleted)
[Windows Mobile] ADB100:
Thanks for the reply.

I managed to find another Manila package (2 folders Core & Engine 2.5.2016) and these seem to work. I will take a look and see if there are any overlapping modules in the other Manila packages I tried.

One other thing that is bugging me is the initial splash screen after flashing - the 'Clearing Storage' one. This is the green WM 6.1 image. The correct 'welcomehead' files are present in the Windows Mobile Build folder so I assume this image is embedded somewhere else - can't figure out where though?

Andy

EDIT: HTCAnimation package was the issue. In the original import of the stock ROM there is a 'HTCAnimationStartup.gif' that is the same as the WM6.1 'welcomehead.png' file. Deleted the file from the package and sanity restored.....
[Windows Mobile] raiderfan247365:
So has anyone got the stock USCellular ROM for the Touch Pro 2 to dump correctly without IMGFS error?
[Windows Mobile] sh4d0w86:
using v1.31...

cooking a gsm rom... with at&t 2.10 as a base.

cooking a cdma rom... with sprint 2.04 as a base.

somehow. when i cook a sprint rom. it has the at&t keyboard layout.

how can i fix this? did i somehow mix up files?

thanks.

sh4d0w86.
[Windows Mobile] airxtreme:
I have never seen that message but it's probably HTC Autorun/RunCC-related stuff.
[Windows Mobile] mechhadi:
Problem with SYS importing

I have downloaded Da_G latest wm 6.1 build, but the following error occured in both 1.31 & 1.32b2 kitchens when I wanted to import new SYS:

"The folder selected doesn't contain a valid dump to parse"

Would you please consider.
[Windows Mobile] mechhadi:
Problem SOLVED
[Windows Mobile] mechhadi:
Building Error, Even if I checked the wince.nls & LangDB in SYS package but the following error occured:

" The wince.nls file is not present in the built XIP. Make sure the WinCENLS and LangDB packages if present were selected and try again: without that file the ROM generation process cannot continue."

Please Help
[Windows Mobile] airxtreme:
Sorry, wrong thread
[Windows Mobile] lokoz89:
hello guys can anyone please help me make a kitchen for the htc ozone (cedar) please!! thanks
[Windows Mobile] Grumps:
Hi there guys

Ok im starting to learn how to cook. just downloaded the kitchen on post one and imported an original rom which is darn old 21854 with manila 2.1. So wish me luck in this new experience. will first try and get it onto win 6.5.x probably 25027 or 23138 and manila 2018. any advise on getting this first step right or links on where to find the right goodies will be much appreciated :)
[Windows Mobile] crazyC:
I see you have a Rhodium. I assume it is GSM?

You can find a stock rom with Manila 2.5 for the Rhodium, the 2.07 base or the 2.10 base both have it. (the ATT 2.10 base has their modified Manila though)

I ended up using the OEM folders from the 2.10 base, but with the 2.07 RILphone.dll added back, and started with the Rhodium 2.07 EXT packages. I then added ones from the latest Leo stuff (but kept with Manila from the Rhodium) and then its a case of playing around.

I would suggest starting with the Rhodium Manila (2012) and then build up as it can be tricky getting all the manila components to work. all the fancy manila stuff can be a bit much for the Rhodium. I also use an old version of the CHT mod (1.6.1 - I think) to keep the memory use lower.

With regards to the sys folder - am currently using 23686 (and also the Huashuan dialer).
[Windows Mobile] Grumps:
Uhm. Now im even more confused :) Mine is gsm yes its a WWE version in south africa. All these things you talk about is obviously all over the place? Id like to just get basic manila 2018 with definately 6.5.5.

MAybe just help me start by telling me where to get the 2.10 base and the rhodium 2.07 ext packages or do you have them bundled that i can somehow just dump it into my kitchen or is it more complicated than that?

Ok busy dloading 23138 from here http://xdaforums.com/showthread.php?t=650783 will see if i can get something to happen :)
[Windows Mobile] airxtreme:
what rollup did you import?
[Windows Mobile] crazyC:
For the 207 rom:

http://xdaforums.com/showthread.php?t=632129

For the 2.10 rom

http://xdaforums.com/showthread.php?t=737168&page=35

Post 346

Not sure I can give a link to working 2018 Manila as I use a hybrid of various builds.

Latest LEO Exts are available on mobileunderground.
[Windows Mobile] Grumps:
Thanx buddy busy downloading. I downloaded this http://www.mobileunderground.info/showthread.php?t=21907&p=51916#post51916 as well its his kithcen. you think it will be easier using that and transferring everything to this kitchen or to start from scratch? also took this 2018 from milski http://xdaforums.com/showthread.php?p=7837649#post7837649 will just keep on reading reading reading. this should be rather interesting :)
[Windows Mobile] crazyC:
Personally (and I speak with limited experience although I have cooked with various devices over the last 4 or 5 years) I find Oskitchen the best, certainly to be starting out with.

It also receives constant attention and updating from airextreme who seems to be quite prolific in his production of new tools.

The easiest thing is that you start with a shipped rom, import it, rebuild it, (untick an EXT package if you want), and flash that. If it works (which it should) then you have your base.

Updating sys stuff is generally very easy as you import the builds using the Oskitchen built in importer.

There are often dependencies with EXTs so sometimes it is not as simple as ticking a newer version. Especially with manila.

I would suggest importing the 2.07 ROM as the base. importing a new sys, and keeping the 2.07 EXTs for the first few runs.

As it is the same device, I am not sure if importing the 2.10 rom will allow you to choose parts or not. Anyway, I just set up a second kitchen and imported the 2.10 ROM, and copied the OEM folder back to my original Kitchen, apart from the rilphone. This left me with the 2.10 OEM folders but none of the bloatware from ATT.

Once you have a good stable ROM configuration, then start playing with the EXTs, and Manila. As I said, don't be surprised if it causes problems, so change only a few things at a time, so you can be sure what went wrong. (Keep a note of whatever version you have called your latest stable one.

I would almost immediately add XDA-UC to your custom EXT folder (probably call it Zcustom or something like that so it gets added in last).

Every now and then take a backup of your entire kitchen (trust me on this).

So as not to get too offtopic, feel free to PM or start a new thread with queries around specific things (but search first - see the sticky) - I am no expert however....just happy to help where possible.
[Windows Mobile] Grumps:
Ok cool thanx for the help. Ill try that. ill start with 2.07 and work my way up from there. im stil trying to grasp all these different folders etc. i dont understand some things like why does XDA_UC has tro be cooked last for instance. does it really make a difference? ill print out the whole directory structure and see if i can figure the rest out. like why one would convert a sys package to an ext package etc. does it affect speed or sumting? Im sure ill get it working all eventually just wanna try and make myself a working rom for personal use :)

Another question. If i would take 2.07 and untick the EXT packages does that automatically exclude all bloatware which i can permanently delete from my kitchen?
[Windows Mobile] crazyC:
Now remember you are only getting my understanding of this.....

1. Unticking all the EXTs will give you a very clean rom, but so clean that it will remove Manila and anything non Microsoft.......

2. I don't think XDA-UC has to be cooked last - but what happens is that for your custom stuff (I have EXTs that add programs, personal settings, tweaks etc) sometimes you want it to overwrite the original files. If you modify the EXT Quick GPS for example, but then want to update to a newer EXT, you will have to modify that as well. If your Quick GPS settings are in a custom EXT that runs last and overwites Quick GPS then you can update the Quick GPS package at will.

Maybe not the greatest or clearest example, but usually its better to have your custom stuff run last.

You can give packages priority in the properties box etc, but its often easier to stick to a simple way.

Really, once you get the OEM folders you want - they don't change much.

Picking your sys is easy.

Then its just about what toppings you want really - in terms of the EXTs.

Sometimes if you modify a sys package for whatever reason, you may inlude it in the EXTs, or OEMs, so that it does not get overwritten when you update to a newer sys.

For example you may want to have threaded email and for that you sometimes need to take some files from one sys and implant them into another.
[Windows Mobile] hthomas:
sorry wrong thread post deleted
[Windows Mobile] Grumps:
Ok now the picture is getting a bit clearer. Im trying to figure out how you choose different packages from different Base Roms if i can call it that. But ill figure that out by playing a bit.

Thanx for all your Help. This kitchen makes cooking look so easy...
[Windows Mobile] Grumps:
Another Question

I loaded a base rom 2.07

It came with Sys 21887

The I imported a few Sys Builds : 23138 and 23569

If i go to the SYS PAckages tab it shows all these things like :

Adobflash

Autoupdate

baseapps etc with dexcriptions next to them

(Does this come from the 2.07 rom I imported?)

Then I go to the OEM package Tab and find

HTC Rhodium Packages

IF i look at for instance OEM drives and open the Package Folder it has a lot of drivers like asyncmac.dll and backlite.dll and battery.dll (does all this also come from the base rom?

Lastly the EXT packages Tab

Adobe pdf

Advanced network

Album

APP service

etc

Also from the base rom?

Dose this mean if i want to update for instance Adobe i simply find the folder and overwrite it with the new version?

Is the dialer and manila and comma manger etc part of thse EXT packages or where do they actually sit?

Say for instance i want to load Cookie as part of the rom does that mean im going to include a full working manila 2016 (unmodified) then add cookie as a EXT package and make sure it builds last so it would overwrite the (Stock Manilla files when building) or do you have to delete all the changed files from the stock manilla fisrt before incorporating the cookie manila files?

I must really sound dumb hey guys?
[Windows Mobile] mechhadi:
The last WM6.1 21054 from Da_G Post, But after that I changed the SYS build with newer one 21057 and my problem solved but my new problem is it couldnot make OS.NB with the following error:

"There was a problem (Could not find file 'D:\Oskitchen\Temp\ROM Generation\Cached OS Generation\Temporary OS Generation\os.nb.payload.new'.) while moving the file "D:\Oskitchen\Temp\ROM Generation\Cached OS Generation\Temporary OS Generation\os.nb.payload.new" to "D:\Oskitchen\Temp\ROM Generation\Cached OS Generation\Temporary OS Generation\os.nb.payload". Please verify that no applications are locking the file in question and click Retry to try again."
[Windows Mobile] crazyC:
Hi Grumps.

Right lets see if I can do this.

The SYS packages all come from the sys build. Hence when you first imported it yes they came from the base rom, but more importantly they were the 21887 sys files. When you select 23569 for example then the kitchen wil only show the 23569 SYS packages.

Generally, just choose the sys you want on the first page and then dont mess with it via the packages. (although you can exclude a few extra things if you dont want them, just be careful - leave the sys alone till you have a bit more cooking under your belt)

The OEM folders are the drivers for the device. Really, unless you update to 2.10, you wont need to touch these much either. Its probably unlikely that a newer rom than 2.10 will come out anyway I would guess. As I said, I had some sleep of Deathe experiences and was advised to try the 2.10 OEM folders, which apart from the rilphone worked fine. If 2.07 works for you - job done.

The EXT packages are those that came with the initial rom and are a good place to start.

I also downloaded the latest Leo ones from the thread on mobile underground and copied them into the directory structure in the kitchen - then refresh package list (right click I think) and they will appear as options in the EXT list. just untick the one in the rhodium list and tick the one in the leo list.

The enhanced (ie HTC dialer) and comm manager are part of the EXTs. My comm manager adds the 3G function at the bottom for example.

For CHT, yes I add the CHT and CHT editor EXTs in my custom section at the end - makes it easier to upgrade Manila parts.

I do add some stuff to the Manila reg entries to hide various tabs etc however.
[Windows Mobile] Grumps:
Lovely!

In your opinion is there a speed/battery advantage over 2.07 compared to 2.10?

Ive used 2.07 for now just batteling a bit to import http://xdaforums.com/showthread.php?t=764933 any advise on this or should i rather try and take manila from this rom http://xdaforums.com/showthread.php?t=784199

Or do you think i should stick to 2016 for now? :)
[Windows Mobile] crazyC:
2.10 solved my SoD issues - if you dont have any such issues, stick with 2.07. Although moving to 2.10 also seemed to make the bluetooth car visor headset thing work properly (ie push the button and it called up MS Voicecommand if you install it)

I use only a few tabs on Manila - home, people, Text, email, calendar, weather and settings. I hide/remove all others to save memory/gain perfromance. I do not want/use the RSS bit on the latest manila.

I think I Pm'd you which Manila components I use? if 2016 is working for you then use it as a base - and play around with updating stuff after that.

I will be honest, Once I had a working Manila I was OK with, inc CHT etc, I would park that and update the rest of the ROM etc and get my customisations in so I was 100% happy with it before taking Manila too much further. You want to be able to flash and then be back to 'fully setup and ready to use' inside 5 minutes (excluding Syncing back up with Activesync etc). This helps a lot when you change Manila and it doesnt work and you then end up recooking 5 or 6 times in a row.....

Also, most of the new ROMs come from Chinese devices and often you are not getting WWE language files. Not sure about the Oboe ones for example.
[Windows Mobile] Grumps:
Ok cool i think ill use 2.10 then with manila 2016 for now with cookie and fbooktab you said i should use rillphone from 207. i guess i just move the folder from oem drivers to the 210 oem drivers folder. leme try :)

thanx once again
[Windows Mobile] crazyC:
with 2.10 you will get the ATT initflashfiles.dat. Also, re rilphone, just copy the rilphone.dll folder - not th whole drivers folder.
[Windows Mobile] Grumps:
ok im lost again what is this initflashfile.dat and how do if get rid of it if need to. Also why wouldnt i want this initflash file? I take it you create subfolders under EXT PAckages with all the extra pss incl manila that you want to add to the rom and remove manila folders completely from the HTC Rhodium Packages folder?
[Windows Mobile] crazyC:
Right, ideally the initflashfiles.dat is short and establishes the system folders and not really much else - everything else should be in the relevent EXT.

ATT cram their roms with bloatware, so the initflashfiles creates a few extra folders in the start menu - its not a big deal. I have not had time to see if dropping the 2.07 one back in causes any problems.

The real world has been very busy recently and as my current rom is very stable (needs some tidying up mainly) I have not had time to cook for a week or two.

You do not need to delete folders from under the rhodium section, just untick the packages and tick the ones elsewhere that you want instead.

In my EXT folders I have a number of sub headings:

Latest Leo packages

Cingular Rhodium

HTC Rhodium

zzHuashuan Dialer

zzzcustom packages

plus a few others.
[Windows Mobile] Grumps:
Ok so if ur using 2.10 how did u get rid of all the bloatware except for unticking all the ATT stuff?

Can you please point me where to find latest leo and huashuan dialer. Also which 6.5.5 are u using or do u stil use 6.5 ?
[Windows Mobile] crazyC:
I simply did not use the ATT EXT files - I used the HTC Rhodium ones from 2.07.

I now have :

SYS: Updated regularly - not tied to particular base

OEM: 99% from 2.10 with the 2.07 Rilphone.

EXTs: A right mish mash but started with the 2.07 Rhodium ones, then gradually swapped out for newer versions from the Leo packages or the ATT ones.

I have been told that the Huashuan dialer does not work with 23569, but does work with 236xx. Not sure. Don't mess with that yet. I will try and post my working setup inc ICR to 4 shared later/over the weekend.

I am using 23686 (whatever com branch that is - I lose track).

http://www.mobileunderground.info/showthread.php?t=15457
[Windows Mobile] Grumps:
Ok thanx so much. I think this will keep me busy this whole weekend hopefully i can get something working by monday.

Im gonna use 23569 then cause thats the last build that has threaded email for outlook and i like that. ill use 2.10 then with all 2.07 pext files. ill just delete the whole ext folder from 2.10 and replace it with the ext folder form 2.07 and transfer the rillphone as well and cook it without removinag anything else and see what happens from there ill try and cook in different manila things and maybe cookie. will let you know how it goes. thanx so much. im pre heating the oven to 180C :)
[Windows Mobile] crazyC:
Check your PMs over the weekend - I will try and setup a 4shared site and share some of the packages and tweaks I use.

23569 was good - I only really moved to try the Huashuan dialer - and also there has been little/no movement on 235xx for a while.

PS - I believe although I have not tried it - that there is an EXT that installs teh threaded email on other builds. I will put that in the 4shared account also.
[Windows Mobile] Grumps:
Ok thanx so much. I think im getting around to understanding the whole folder structure and how to do this. I created subfolders in EXT packages called 207 Files and 210 files cookie and will work on them so i can select whatever i want from whichever rom.
[Windows Mobile] thecrazyman64:
Error: 0x8000000a

I am a new chef, right now cooking just for myself.

A few weeks ago i tried to cook again a new ROM, after learning some things and i got an error. I posted on the "Make your own ROM" thread but nobody answered [click].

I tried to import the ROM again and cook without my tweaks and the whole build process went well. After that i imported the ROM again and made my kitchen again, without closing the osKitchen and the build process went well but the ROM didn`t boot.

Is anyone kind enough to help me?

Thanks in advance!

ps. Sorry for my bad english! :)
[Windows Mobile] mudhi:
Hi, airxtreme, as a beginner, this is the only kitchen I managed to cook a working rom, great work! I just have to import new sys, tweak some ext or sys files, module to file the ntfconfig.dll, no recmod, and I saw that the build log, slot 0 - 0 modules... the ROM is also working on perfect performance.

Thank you...
[Windows Mobile] mechhadi:
Hi airxtreme, finally I managed to import an stock WM5 ROM and WM6.1 SYS (21057) but I couldnt finish the job because the kitchen couldnot make OS.NB with the following error:

"There was a problem (Could not find file 'D:\Oskitchen\Temp\ROM Generation\Cached OS Generation\Temporary OS Generation\os.nb.payload.new'.) while moving the file "D:\Oskitchen\Temp\ROM Generation\Cached OS Generation\Temporary OS Generation\os.nb.payload.new" to "D:\Oskitchen\Temp\ROM Generation\Cached OS Generation\Temporary OS Generation\os.nb.payload". Please verify that no applications are locking the file in question and click Retry to try again."

Would you please help
[Windows Mobile] airxtreme:
You have to use the implantxip build method (found in advanced tweaks) since the ROM for unknown reasons has no ULDR partition.
[Windows Mobile] Mr.zeus:
1- i can't change rom version

its name is always the offical nam (for expl: 1.27.... wwe)

but roma date change correctly

2-which pkg have problem when in bulding rom, the kitchen tell an eror about RUNTIME ?

it says one of the .exe of kitchen (i dont remember the name) needs RUNTIME & u dont have it. but when i change the EXT completly.. there is no eror

sorry for my bad english & low knowlege

(cooking 6.5 (mega rom) for OPAL.... Win XP , 7)