Database Info

ROM Kitchen questions

Now perhaps i am being a little naive here, but surely if you wish to cook a custom rom for yourself, the best option by far is a kitchen with an ultra clean rom with absolutely no customisation at all, and then a massive repository of custom apps etc as tick boxes in the buildos screen?
I have cooked myself a few nice roms using pandoras kitchen, but realise that there are even with it a few addons within the base rom itself. I am looking for the cleanest of base roms, then use the kitchen with all the OEM packages i can find.
Also looking how to create a wap provisioning file that can integrate to the rom at build stage to set up my O2 gprs and wap settings, instead of doing it as a cab in extended rom.
Any help and suggestions are welcome, and big thanks to all the usual suspects for continually releasing little golden nuggets for the rest of us

Well, yeah, a little...
Anyway, if you want to try taking things out of the sys directory, (usually the "base os") just remove the offending subdirectories and they won't get built in.
For your wap settings, just create your own package. (Read how in double0_four's kitchen thread, or faria's kitchen thread) Just put your reg settings in the .rgu file. Or you could tack your settings into another .rgu file that's already being built. (Not the best form, but it should work.)
Have fun!

For each of the components in the SYS folder, you can add an entry in the options.xml file in the SYS folder. Use Office and Transcribe as an example of how to do it. This will allow you to choose what you want from the BuildOS screen.

I dont think you can build GPRS settings using a reg file??? I have scoured the registry and cannot find how it is done. The last time i did it i used a cab file with a <wap-provisioning> style xml file, buti dont see howthis would built in an .rgu file.
And which rom would you consider to be the leanest rom to build from, then i can just make up my own packages to add in to it.
If worst comes to worst, i will just use the cab andset it to run on first boot, same way one ofthe other roms does this instead of using extended rom,. they just put the cabs into the windows folder

Updated official ATT ROM CE 1.61.502.2

So with all the cooked roms im sure this isnt going to interest alot of people but will post it anyway.. Looks like the only thing that changed was the CE version and some things added/removed/fixed.. Nevertheless, Enjoy!
From
Software version
GSM Radio: 1.27.14.09
Protocol version: 22.45.88.07H
CE version: 1.60.502.3
OS build: Windows Mobile 6 AKU 0.4.4 Build 18128
To
Software version
GSM Radio: 1.27.14.09
Protocol version: 22.45.88.07H
CE version: 1.61.502.2
OS build: Windows Mobile 6 AKU 0.4.4 Build 18128
Feature Added
Add MTV Cribs
Issues Fixed
Remove MySpace
Fast Forward and Rewind don't work with BT headset
Complaints of excessive background noise, BT HS, noisy
environment - Using BT Mot HS820.
Volume control doesn't work with BT.
The HTC phone failed to provide the capability to adjust the
audio volume.
MSN-Not able to block the contact.
Wrong user message to invitee when group membership
invitation is accepted.
Download me here

I'm new to this forum but I'm currently using Schap's 4.3 and Radio 1.27.12.17 on an ATT Tilt. Been having issues with static over the BT. Do our cooks take anything from oem roms? I'm hoping that the fixes in this rom get incorporated in the next version of cooked roms.

Great work. Any idea the date that this was released? Also, even though its not listed, any word on video performance?

thanks for the ROM

Nice work mate!

Is this a shipping ROM, from currently sold devices? (Nothing is altered?)
Thanks

this would be a shipping rom, not an altered or cooked rom.... this is not currently released by ATT yet

I figured, what the heck. I'm a flash-a-holic now...
Trying it out to see what happens. Might try cooking it myself too (if I'm feeling crazy enough).

Can anyone else verify what I am seeing? I am cooking with this ROM atm, and I am getting some new icons in Settings -> Connections: SMS Service, CSL Line Type (or something like that), and one other I believe. I actually removed the ROM from my device for the time being, but I would love to hear if anyone else is seeing that.

its nice to see HTC and AT-T making more roms for the kaiser~ they let us hermes users in the dark for a while

Thanks ,will try it tomorrow

its a oem rom so fulll of bloatware like game demos and appllications that encourage you to spend more money on your service plan its just ATT capitalizing ,nothing personel only business ! BS

Shadow7789 said:
Can anyone else verify what I am seeing? I am cooking with this ROM atm, and I am getting some new icons in Settings -> Connections: SMS Service, CSL Line Type (or something like that), and one other I believe. I actually removed the ROM from my device for the time being, but I would love to hear if anyone else is seeing that.
Click to expand...
Click to collapse
SMS Service and CSD Line Type are in the original 1.60 rom, but they are removed from connections menu through some registry edits in the operator package. You can get them back along with HSDPA by editing your registry.

are you serious about that MTV cribs thing that cant be a real app

Thanks for the response.

looked into the rom a bit and didn't find too many changes. lots of things i don't use seem to be updated including ptt, telenav, oz and some other bloatware. the only notable changes include and updated wavedev.dll and the following registry entry:
[HKEY_LOCAL_MACHINE\Software\OEM\Bluetooth]
"PhoneVol"=dword:C8 ; Default value : 200 (GSM_GAIN_4)
also in the operator package there is an addidtional entry:
<!-- ATT Reject Msg is enabled. 2007-12-10 -->
<characteristic type="Registry">
<characteristic type="HKLM\Drivers\BuiltIn\RIL" translation="filesystem" >
<parm name="EnableATTRejectMsg" datatype="integer" value="1" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
not exactly sure what that does. the SYS folder seems to be identical to 1.60.502.3

akadonny said:
looked into the rom a bit and didn't find too many changes. lots of things i don't use seem to be updated including ptt, telenav, oz and some other bloatware. the only notable changes include and updated wavedev.dll and the following registry entry:
Click to expand...
Click to collapse
i would imagine those changes there were to fix the volume problems as stated in the fixed section.

leoiden said:
its a oem rom so fulll of bloatware like game demos and appllications that encourage you to spend more money on your service plan its just ATT capitalizing ,nothing personel only business ! BS
Click to expand...
Click to collapse
Don't like, don't use it.
Thanks OP!

Cab with Audio Fix
For any interested parties, attached is a cab with the dll and registry entry. I personally don't use any kind of bluetooth headset so I can't tell you if this actually improves anything.
Edit: cab removed. seems to kill all audio. sorry about that folks. just unintstall and audio returns.

I frequently use a bluetooth ear piece so I'll be installing this to see if theres any change

How to get OEM Cabs?

How does one extract a CAB from a ROM?
For instance if I want to cook my own ROM, but I want to use some of the applications in say Dutty's latest release, how do I get those cab packages to install on my own?
Particularly, i am interested in pulling the latest remote desktop off of the latest test Tilt ROM because it has the ability to map the mobile's local storage.
thanks!

one word: RTFW.
Read The FFing Wiki!!

If I could find it on here I wouldn't have posted asking about it.
This is the first of my posts that have been met with a response like this, but honestly go troll somewhere else. It is 0% productive to make responses like that. You are cluttering up the forum with usesless posts (as much as I would be guilty of if this is indeed described in the wiki). If it's in the wiki, why don't you point me to where?
The wiki isn't a single page as much as you'd like to believe, it' links to hundreds and thousands of posts of information.
I have CIM and SIM unlocked my device, flashed about 5 different ROMS and radios and done numerous other things with info I have gotten from the wiki. I read through the ROM cooking kitchen tutorials, but could not find anything which mentions my task at hand. I found information and links on the cooking tutorials to use OEM cabs that people had already extracted....but what if the one I want isn't there? Where is the info that tells me how to pull one OUT of a ROM (instead of putting one already extracted IN)?
So, either you are misunderstanding what i want to do, or else the way i am phrasing it is misleading, both to you and to myself, which is maybe why i can't find the info I want.
So, please your brilliance, point me to location in the Wiki that would describe a procedure where i would be able to extract a .CAB (like Windows Mobile Desktop) from the latest AT&T test ROM.
Otherwise your contributions to this thread are unwanted.

while maarten might have pointed you in the wrong direction, your thread is still a redundant one. if you tried to search, you will find lots of threads covering this subject. and yea, your search results are probably gonna end up with tons of threads that end up looking like this thread, but if you sift through the results.......and by sift i mean u really really sift, i promise you, you will find something useful.

Simple Answer...
...You can't extract a CAB from a ROM usually.
Explanation: In the ROM itself things like windows live are extracted from the CAB already and are installed, so the CAB itself is not there. If your original question was how do I extract the files needed to MAKE a CAB.. then that's more complex, a different question, and a waste of your time if you don't already know how to do it.
If you really want to learn you will have to search.. if you just want a CAB of the latest windows live messenger get the build number by installing the ROM and looking in the application for it.. then use the google search of xda-developers (e.g. "Windows Live" <build number> )and you can be sure you will find someone has already done the hard work for you.
hope that helps.

You find threads on converting CAB's to OEM packages but not the other way round.
The trouble is when you extract a ROM, you'll probably find in the SYS directory, the OEM folder you want with all the relevent files. BUT you won't know where they all go. And if the files you want are in the OEMApps folder you won't know what files need to go together. What I do is look at a similar OEM package (See Alex's excellent work) and this will show the files you need, where they go plus any registry settings. You can probably copy over the newer files from your extracted ROM to the OEM package, overwriting the older files.
If the OEM package doesn't exist it will be a long, long job!! You need to search through the files on a device with the installed ROM and make a note of the location of the application files - this is required for the install.txt file. The next problem (& the major one) is to find any relevant registry settings - again you can search through the registry of the installed ROM. Now all this take a lot of time and effort...

odyseus said:
The next problem (& the major one) is to find any relevant registry settings - again you can search through the registry of the installed ROM. Now all this take a lot of time and effort...
Click to expand...
Click to collapse
You can cheat a little bit here though, some apps will recreate any missing entries with sensible defaults if you leave them out.. others wont.. for those you can find ANY version of the CAB that you want to use (even an older one say) and use its registry as a guide to where to find the ones for the new version.. the registry locations dont change that much between versions usually.
you'll still get issues.. but in most cases this helps if not works

Thanks for your info sambartle and odyseus. I had feared as much based on what I had found through search already, but thought there might have been a way... I guess _Alex_ and others do quite alot of legwork to extract and make all these things themselves.
I can't quite understand it however.... If I take a windows PC for example (which is similar in it's registry) I couldn't necessarily find all the associated files and registry keys associated with an application. If you are lucky they are all under one folder and one key of the registry... but something like MS Office installs so many shared files, and classes objects into the registry it would be nigh impossible to recreate that (even given the time).
Unfortunately, if the last posts I read are accurate the developers here won't be providing new OEM dumps for a while. Maybe once 6.1 is more widely released microsoft will allow download of the new mobile desktop.
Ah well, thanks for your help.... and to the other posters...it's worthless posts like yours that contribute nothing to the forum that makes extracting useful information through the forum more difficult than it should be.

bengalih said:
Thanks for your info sambartle and odyseus. I had feared as much based on what I had found through search already, but thought there might have been a way... I guess _Alex_ and others do quite alot of legwork to extract and make all these things themselves.
I can't quite understand it however.... If I take a windows PC for example (which is similar in it's registry) I couldn't necessarily find all the associated files and registry keys associated with an application. If you are lucky they are all under one folder and one key of the registry... but something like MS Office installs so many shared files, and classes objects into the registry it would be nigh impossible to recreate that (even given the time).
Click to expand...
Click to collapse
It requires alot of testing and re-installing or re-flashing, sometimes on the same ROM, sometimes on different ones, just to iron out the bugs. It's one of the reasons why I released AT&T and HTC versions in the past, just so that I can have two platforms to test on.
Windows CE is alot simpler than Windows XP by at least 10 fold. Yet there are people who have created portable versions of Microsoft Office through the use of deployment applications like thinstall, so anything *IS* possible, with automation.
Automation that works at the functionality of thinstall for CE doesn't exist because of economies of scale (e.g., it's not worth any developer's time to create a deployment package as robust as Thinstall for the PPC).
bengalih said:
Unfortunately, if the last posts I read are accurate the developers here won't be providing new OEM dumps for a while. Maybe once 6.1 is more widely released microsoft will allow download of the new mobile desktop.
Click to expand...
Click to collapse
Dumping and stripping is relatively easy once you've gotten the hang of it. You just need to keep at it.
Personally, I just don't find it to be challenging any more, since I've done quite a few AT&T/HTC WM6.0s and HTC WM6.1s and I'm now waiting for an official shipped version (no more leaked betas!!!).
bengalih said:
Ah well, thanks for your help.... and to the other posters...it's worthless posts like yours that contribute nothing to the forum that makes extracting useful information through the forum more difficult than it should be.
Click to expand...
Click to collapse
Your initial question / thread starter didn't have many details, so I would have flamed you too, although I would have also provided a link to my OEM Package Tutorial (Creating Packages from ROM files section)
It never hurts to be overly verbose when asking a question. This would make the flamers leave you alone (because they'll just get tired of reading) and should *NOBODY* respond within a couple of days, when you bump it (with flowery encouraging yet challenging words, like 'You guys are so great, but nobody could answer my question?'), nobody will mind that you did, and you will get answers after that bump...
FWIW, I still think this should have been a question asked in the OEM Tutorial thread, which I have subscribed and respond to much more frequently than new threads which I'm not aware of until I actually have the time to READ new threads. It's also because, should anyone have similar questions, it'd be much easier to fiind in the bigger OEM Tutorial thread than in this one...
Hope this helps!

Thanks Alex... as you said you would have provided me the link to your Creating Packages from ROM section which I did gloss over briefly previously but didn't totally see how it helped me (since I was looking for Cabs). But, now that you point me there I again I took another look and got some useful information.
So this is where i am at:
Ok,
So first I extract the ROM using your kitched script, then in the SYS folder I find two folders that seem to be what i want:
RemoteDesktopMobile
RemoteDesktopMobile_Lang_0409​
Inside the first folder are subfolders with names like:
MvkLib.dll
and
wpctsc.exe​
and inside those are an actual DLL or EXE file, and some other files called imageinfo.bin, imageinfo.txt, and some files S001, S002, s003, etc...
I am going under the assumption that all I need is the .DLL file, and the rest are some sort of uncompiled form of the DLL? (Please let me know if i need to pay attention to those other files.)
So I take all those DLL and EXE files. I also look for and find an INITFLASHFILES.DAT and don't see any references to these files, so i assume they all go in \WINDOWS?
There is also an RGU file inside here that has a few registry keys for this application.
Inside the second folder is just a DSM, and a couple of .txt and .htm files. Since these files aren't in INITFLASHFILES.DAT either, I assume they just go in \WINDOWS?
I also find a provxml file in \OEM\OEM_Lang_0409 called mxipupdate_RemoteDesktopMobile.provxml.
The contents are:
Code:
<wap-provisioningdoc>
<characteristic type="FileOperation">
<characteristic type="%CE11%" translation="install">
<characteristic type="MakeDir" />
<characteristic type="Remote Desktop Mobile.lnk" translation="install">
<characteristic type="Copy">
<parm name="Source" value="%CE2%\wpctsc.lnk" translation="install" />
</characteristic>
</characteristic>
</characteristic>
</characteristic>
</wap-provisioningdoc>
Based on my reading of the links off your page and some further research this file seems to say the following:
Make a directory (if it doesn't exist) called \Windows\Programs (%CE11%)
Make a shortcut in the directory called Remote Desktop Mobile.lnk (the decimal ASCII text) that maps to \Windows\wpctsc.lnk (%CE2%)
So... now I have:
A handful of files...I need to put them in \Windows
I have an RGU file with a couple registry entries I need to import into the registry
I need to make
a shortcut to the exe int the \Programs directory
How then do I now package all this up into a CAB that will automatically perform the above operations?
I know about "makecab" to actually package all these up into a cab. But how to i write the command file that tells it how to do all the provisioning and registry entries?
Please let me know I am on the right track.
Thanks!

Ok...I found a program called WinCE Cab manager that made the process pretty easy. I installed it on my device and it seems to work well.
I have uploaded it here:
http://rapidshare.com/files/104977265/Windows_Mobile_Desktop_6.1.cab.html
Where is the appropriate place to post this to share with others?

yeah like people have said dumping the rom is the way to do it but most roms nowaday dont have the files for you to recook(so no oems)
so the best thing is to do is get the cab yourself and convert it to an oem with ervius's package creator

sorry kidnamedAlbert...I'm not sure where you were getting at there... the whole point of my post was how to get those cabs made from the ROM in the first place. As you can see from the previous posts it seems I have already resolved (or started my way to) getting this done.
Personally, i prefer to have the cab file as I am more interested on just being able to install it on my device then cook it into a ROM. If someone wants to cook it into a ROM that seems to be a well documented procedure if the cab file is already available.
In my case, there was no cab file available for the latest version of Windows Mobile Desktop...so i made my own from the ROM.

Maarten_0031 said:
one word: RTFW.
Read The FFing Wiki!!
Click to expand...
Click to collapse
One word: RELAX and STOP SWEARING, geez.

Help Creating a CAB from XML

I'm trying to add a registry key for Microsoft Activesync DeviceID's so I can manage mobile devices at work and restrict OWA access that fails to meet one of the pre-approved device ID's we've approved. Unfortunatly after I create the _setup.xml and run the makecab _setup.xml Activesync.cab it fails to run properly. Can someone take a look at my code below and see if I missing something?? For security reason's I've * out the value of the deviceID.
<CODE>
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKCU\Software\Microsoft\ActiveSync">
<parm name="DeviceID" value=***** datatype="string"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
I'll be honest I thought this was pretty simple until I've spent the last several hours trying to figure this out. The only CAB that was sucessful was the one that I had created via
http://triton.homeip.net/RegistryChanger/index.php?e=1
If you look at the ActivesyncDevice and create that cab it runs sucessfully on my device and the registry is changed properly. In the end I guess I can use that cab, but really I'd like to understand why mine isn't working as opposed to always using this website. (Still thank you for the website) The only thing that comes to mind is maybe I'm created the cab incorrectly??

Nevermind. I'm an idiot... Forgot the quotes around the device id. DOH!!!

More Info...
Can you provide a little more info on how you're managing your devices?
Specifically, how are you creating the deviceID's for your devices?
Also, have you had any instances where the deviceID changes after a hard reset or some other set of circumstances?
If one of your users does do a hard reset, then do they have to rerun your CAB file so that the correct DeviceID gets set?
Thanks,

[A] Work URL Exceptions

Hi,
i am searching for the "Work URL Exceptions" in the Windows Mobile 5 registry, but i cant find.
Anyone a idea where i can find it ? I need it for provisoning!
Or has anyone another idea for provioning the "Work URL Exceptions" ?
Thanks.

Ok, it takes a while but i found something.
Code:
<wap-provisioningdoc>
<characteristic type="CM_Mappings">
<characteristic type="16777216">
<parm name="Pattern" value="*://192.168.10.15"/>
<parm name="Network" value="{A1182988-0D73-439E-87AD-2A5B369F808B}"/>
</characteristic>
</characteristic>
<wap-provisioningdoc>
This code SnipIt adds the IP 192.168.10.15 to the url exceptions list.
These exceptions should be numbered from 16777216 to 16842751.
Link:
http://msdn.microsoft.com/library/d.../html/wce51howConnectionManagerURLMapping.asp

Not sure if there was a specific reason you were looking for it in the registry, for a program your writing?
I have 6.1 on my phone, so I'm not sure the location is gonna be the same. But on 6.1 you go to the following;
Start > Settings
Select Connections tab
Select Connections icon
Select Advanced tab
Select Exceptions button
After I did that, I was able to do a search for what I added to find the location in the registry.

I need it for provisioning, i have to configure 30 PDAs, and i dont wont to do it manually.
I had the same idea, add a exception and search in the registry....but i dont find anything i add. Anyway now it works.
HTC Touch Diamond
WM 6.1
German Vodafone ROM
bye

Hi, can you explain how you apply this xml provisioning file ?
I have to configure 600 PDA and i'd like to use a SD Card to update configuration in a single operation (using the autorun mecanism of SDCards)

smotrs said:
Not sure if there was a specific reason you were looking for it in the registry, for a program your writing?
I have 6.1 on my phone, so I'm not sure the location is gonna be the same. But on 6.1 you go to the following;
Start > Settings
Select Connections tab
Select Connections icon
Select Advanced tab
Select Exceptions button
After I did that, I was able to do a search for what I added to find the location in the registry.
Click to expand...
Click to collapse
Hi,
What was the registry location for the work url exceptions? I tried the same steps then did a registry search but that didn't find the entry I created.
Thanks for your help.
HTC Touch Diamond
Windows Mobile 6.1