yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] doctajay:
I have to be doing something wrong in this cooking process. I have read the instructions over and over again and yet I still get the GuestOnly Problem, but if I use Duttys ROM or any other ROM by our XDA Chefs, it works fine. I switched computers, and cooked, and it still happened, so I think I'm doing something wrong in the process. I want to tell you exactly what I'm doing so you can tell me if I did something wrong:

1) I set up my kaiser kitchen exactly as you told (using an ATT 1.61 ROM)

2) In the Base ROM folder, I put the RUU_signed.nbh there. I didn't extract it. I just left the .nbh in that folder.

3) I opened up the Kaiser Kitchen scrpit and pressed: C.

4) I navigated to the kaiserkitchen folder where everything was and the program loaded the packages.

5) I didn't click any extra packages. I just left it how it was.

6) I clicked Go or Build or whatever is there, and it built it with no problems.

7) It went through the black screen with scrolling text. I noticed that it said that it couldn't find boot.hv and something else, but it didn't stop the process, so I ignored it.

8) The Build OS program poped up and I chose my OS-new.nb file that was just made and the radio that was included in the ROM folder.

9) I clicked build, and things proceeded fine.

10) I closed the screen and the PagePool Tool popped up. I left teh pagepool at 6, and pressed close.

11) Then I flashed the ROM and that went fine too.

12) When it reboots and connects its still guest only.

I feel like I'm making a mistake in the beginning. Am I supposed to do anythign with the OEM, ROM, and SYS folders? Am I supposed to extract the ROM in the baserom folder first? Do I copy anything and overwrite anything in the OEM, ROM, and SYS folders? From my instructions, did I make any mistakes.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gthing:
Ah yea, sorry - I had intended to post my OEM package for Batti last night but I stayed up so late cooking that I forgot. Hopefully I'll be able to squash these last few bugs and start going to bed earlier than 5am! :D

Alex - great idea on the provxml files. I found a setting for OBEX in OEM\OperatorPKG\mxipupdate_oemoperators_101.provxml and changed it to enabled. I flashed the new ROM and it was still disabled so I looked some more and found another setting in Packages\ATT - Proxy Settings\mxiupdate_oemoperators_101.provxml. I've changed it to enabled and will report back if it works.

I also had the same idea about windows live search - not cooking it in because I like getting the updates. My problem is coming from when I try to install it afterwards.

I've tried about every combination of NETCF packages and CE SQL packages that I have found and I am still getting that "Microsoft.WindowsMobile.Status or one of it's dependencies is missing" message when I try to run live search. I've even tried installing NetCF and CE SQL post flash and am running into the same problem, so I think it goes deeper than the packages themselves. Perhaps it's a problem with the AT&T 1.62 Cooking Kit?

Here is the full error in case it helps:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gthing:
After you have flashed the ROM, can you look at the registry and see if [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE Services]

GuestOnly"=dword:00000001

is set to "0"? If not then something in the rom is messing with with that setting, either an RGU or provxml file.

Also, Alex made a good suggestion earlier of moving all the packages you weren't going to use from packages to packages-deleted. Some of those packages install even if they are not selected and might cause some problems.

Also, not finding the boot.hv files is fine, as the process makes its own.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] stainlesspc:
I used the same radio I used with Alex's Ultra clean which is where I got my base rom from.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gthing:
I've done a little more digging on my Net CF issue and found this registry key:

/HKEY_LOCAL_MACHINE\Software\Microsoft\.NETCompactFramework\Installer\Assemblies\Global:Microsoft.WindowsMobile.Status, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35

and it is set to

\windows\GAC_Microsoft.WindowsMobile.Status_v1_0_0_0_cneutral_1.dll

I can confirm that this file exists and his hidden using Total Commander. I'm not sure what other links there are that are supposed to be involved here, but from this it looks like everything's in order.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gthing:
What is the version number? WM6.1 is very picky about which radios work with it.

Try one of these:

WWE: http://www.4shared.com/file/3672445...582620_CustomRUU.html?dirPwdVerified=b82fbf61

UK: http://www.4shared.com/file/3672302...640821_CustomRUU.html?dirPwdVerified=b82fbf61

These should not be destructive to your current ROM (If you have 6.1 running now), but back up your data just to be safe. :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] doctajay:
When I look in the registry, there isn't even a Guest Only entry. I tried to add one by making an .RGU file, but it didn't work.

What about the BaseROM folder. Once I put the RUU_signed file in there, is that it? Or do I need to Press "e" in order to extract the ob.nb file? And when I extract it, do I then put it into the ROM folder?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] doctajay:
I know it probably won't matter, but my bootos log is attached:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] stainlesspc:
Thanks gthing I will try the last one.

I tried the other one already.

Since you seem to be fielding most questions tonight.

Is there a way to tweak an already cooked ROM without having to start all over ?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gthing:
It depends on what you want to fiddle with. You can mess with the registry, radio, and somewhat with the applications and files. Beyond that, you pretty much just have to recompile and keep flashing!

I think half the fun of cooking is trying to figure out what to do with the time while you're waiting for your ROM to come out of the oven, and then realizing you need to make one minor change once it does! :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
FWIW, doctajay was working on a set of videos, and the corrections I've suggested should be helping his cooking issues as well...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] doctajay:
Thanks alot Alex for the help. I followed your instructions and neither my laptop or desktop will come out of guest only, but its ok. I know that my technique is perfect so it must be some random unknowable bug. I will still work on the videos and send a link to you first to proof read (if thats ok :) ).
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gthing:
Has anyone else cooked a rom using the latest AT&T 1.62 release from Alex and been able to install Windows Live Search Mobile?

This is a nagging bug and I don't even know where to look for a solution. Any help appreciated.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
It worked fine for me on the 1.62 Home ROM. I suggest removing your packages one by one to determine which package is causing a problem with Windows Live Search cab.

Same advice goes for Doctajay, but I suggest removing all packages and seeing if the guest issue still exists for you to start with.

Hope this helps!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Alemaker:
Windows Live Search

I've found that, for me, cooking Windows Live Search isn't the best route. They update it too often. I just use the tier-install and let it install as a cab, that way I can uninstall it if I want and not have it uninstall denied cuz I cooked it in.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Yeah, he's trying to install it as a cab too.

FYI, I found out something new with Tier Autoinstall. If you put all your cabs into \Storage Card\Boot it'll find it there :D I'll be updating the wiki with this new information shortly.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jbcross:
just to clarify.... assume you mean \Storage Card\Boot........ not

Storage Card\Storage Cab\Boot

And thanks for all you do!!!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Yes. Thanks for noticing my typo! Original post edited too...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gthing:
Alex: I just tried a few minimal roms containing nothing but different combinations of netcf and sqlCE. I even tried some different OEM packages. But nothing worked. I still get that same netcf error.

So I redownloaded the kitchen, re-downloaded your AT&T 1.62 ROM (although the rapidshare folder says 1.82???) and re-downloaded the packages collection (which doesn't seem to be in the rapidshare folder at all anymore).

Now when I flash a rom created with my new tools collection, I can't even get an internet connection (errors out, no connections appear in config), and I can't install cab files so I can't see if live will install now.

<sigh> So I'm working on dumping the factory ROM right now and got so far as to have a bunch of .nb files. I might be giving up on this whole idea soon...

edit: Here's an idea: do I also need netcf 1 installed? Do I maybe need 1, 2, and 3 installed for 3 to work?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
As dumb as this sounds, make sure you have all your windows updates, especially .NET 2.0 SP1 and .NET 3.0 SP1, as .NET framework is used by BuildOS and the ROM tools.

As far as .net CF goes, you only need 2.0 for apps to work. 3.5 isn't in any shipped ROM yet, almost no apps use it, but it is faster. However, not all apps can use it.

BTW, as for weird issues, that happens to me *ALL* the time. I can't explain it myself. On some days, my kitchen will only produce duds. On others, I'm cranking out ROMs like no tomorrow.

Hope this helps!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] JoeWilcox:
Some registry settings seem to appear in multiple RGU files. For example:

HKEY_CLASSES_ROOT\SystemFileAssociations\image\shell\save\Save Location

That is defined in 3 rgus. Do you know the order in which they are processed.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] stainlesspc:
HELP Cooking and Cooking but keep getting wrong ROM

What am I doing wrong.

I am cooking like a fool and everything is fine.

I am getting the packages I put in and everything works fine.

BUT I am trying to get a 6.1 ROM and I keep getting 6.0.

I have pulled the RUU_signed.nbh out of every6.1 I have and even tried a couple others.

I cear out the BASE ROM folder and insert the new RUU_signed.nbh.

I extract, cook and biuld, page pool and flash

then Presto my new 6.1 rom turnes out to be 6.0

What am I doing wrong
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jbcross:
Battery Icon Puzzle

I have been have a great time with this ROM cooking stuff. I have been bouncing my head against the wall relative to battery icons. No matter which ones I selected to cook in there are problems. For example the non standard one would show for a while – an hour, a day, but then revert back to the standard battery icon.

Then another problem started where by what ever condition the phone was in when booted (charging or running on batter power) the icon would remain constant – so if it boots when plugged in and I then unplugged it, the plugged in icon would remain on the screen. This condition was the while chefing up 6.0 or 6.1.

I did everything I could think of… adding back packages one by one, to no avail.

Finally I decided to use the auto connection wizard, rather then running my trusty CAB from shogun that has stood the test of time for my x treo 750 and my x tytn1, and it seemed to do the trick. I have tested it several times with several different home cooked roms. It just seems totally implausible to me that this is the actual solution. Is there any logical explanation to this?

** I have searched for a solution and found nothing, obviously or I would not bore you with this long winded post. It may seem like a small annoyance but you have give us this tool to make our devices exactly as we want them….etc
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Why are you extracting? All you need to do is download the ROM folders, put them in the right places and press C for cook... Make sure you have no stray .nb files lying around too, and always empty out your temp dir. Hope this helps!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Have you taken apart the cab and made sure it doesn't do anything extra? It's quite possible that something in this cab just isn't good for a Kaiser. You could always make it into a OEM package and examine it's contents...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Can't recall the exact order, but if you look at the BuildOS logs, it will show you the order of precedence.

Hope this helps!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] stainlesspc:
Alex -

OK now :)

I Think I finally got it figured out. I was using the wrong Sys and Rom packages.

But one question for now.

Once I finally got 6.1 to work none of my buttons worked.

When I went to Buttons in Settings,it was blank.

Did I miss some package or what ?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Alemaker:
New OEM folders?

Alex,

Did you say that you are putting up new OEM folders? I don't see any on rapidshare or megaupload, or am I missing something?

Alemaker
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Check the wiki, I believe thomassster put out a fix for 3.02's button issues.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Been busy. Had to remove all OEM folders because of some software that shouldn't of been there. Will try to upload this weekend.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Alemaker:
A quick request if I may?

Would it be possble to move IE7 out of the Office folder and have it install on the main program screen?

Alemaker
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Alemaker:
One last request,

Any possibility of adding a BT OBEX package?

Tried just changing the reg key, but no luck, and searched the forums for a package, no luck either. :(

Alemaker
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gthing:
A package will do you no good as the registry settings will be reset by the provxml files contained in the ROM.

I just dealt with this same issue!

Go a page or two or three back in this thread, I have posted where you find the files you need to edit. Once you edit those, you'll be good to go.

edit: here's the link: http://xdaforums.com/showpost.php?p=1953453&postcount=431

To answer your other question, to move internet explorer into the main folder you will need to edit OEM\OEM_LANG_0409\initflashes.dat. You will find where the link is created in there and be able to just remove "office" so it lands in the programs folder.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gthing:
Good news! I reinstalled the whole kitchen/rom/packages AGAIN, updated my .net stuff, and finally built a ROM with working net CF! Thanks Alex for all your help! I couldn't be more excited!

Here's one more bug I've run into. I'm making a OEM package that will remap the left softkey to "New SMS." I've got everything working except BuildOS pukes on trying to enter the registry keys:

(for some reason vbulletin insist on adding a space in "112," but it's not really there in my .rgu)

I can't figure out what I've done wrong there, but buildOS sure doesn't like it!

edit: I finally found the answer, so here it is in case anyone else runs into this problem. The slashes must be escaped when calling the directory. So the line should read "Open"="\\Windows\\newSMS.lnk"
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Alemaker:
thx gthing:)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] stainlesspc:
Ok next new cook question.

I thought I finally had all my 6.0 and 6.1 stuff seperated and setup yo cook

butnow I have a seamingly good 6.1 ROM but it reads as D 1.60.0.0 durring boot ?

Plus Deveice info and backlight are gone from settings,

what did I do this time :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] slimshadee:
Alex:

A VERY small bug found..

As thomassster states above, he "created" a package for the above fix, which you have linked in the WIKI. It has a UUID conflict with your package "Registry-beam disabled". I suspect he just edited the beam disabled .rgu to build this package. You may want to update this package to correct the UUID conflict (2e9850dd-7576-4da4-ad2b-0c19be831f88).

shadee
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Alemaker:
Tried your solution for OBEX, and 2 things:

1)the reg key defaults to 0 no matter if I change the provxml,

and

2) There is no option tab in bluetooth settings to access it, like there is in an original ROM.

The fix of IE7 worked good though. :)

so

@Alex,

I'm not sure how to do it but, could you add BT OBEX back into your kitchen??

Alemaker
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gthing:
You have to remember to find *all* instances of the obex setting in the provxml files. I changed it in the OEM and still didn't have obex enabled, then I found it in the AT&T proxy settings package. I also added the registry tweak manually through my own cab (which didn't work).

So like I said, you can have an obex enabling package, but it's just going to get overwritten by some rouge provxml file.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] dniitani:
V5 OEM Packages

Alex,

Any estimate as to when the OEM packages will be uploaded?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gthing:
I've narrowed down the problem to the last line where I link to the new.sms file. This key works when I put it in on my device, but for some reason it keeps buildOS from working.

As far as buildos is concerned, it shouldn't matter what is in the string, right? Basically I just have newsms.lnk sitting in the OEM packages folder, although it loses the .lnk extension and becomes a shortcut.

Any ideas?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Alemaker:
O.K.

I give :eek: Just changed the one,

thx for the IE7 tip though, that worked out perfect.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] stainlesspc:
Help Please how do I fix missing items in Settings

A couple things

FOr some reason I shot "D 1.60.0.0" when my tilt boots but it is WM6.1 3.02

Also I am missing several items in the settings menus.

THe items and *.ink files are in the win dir and I can copy them to the Start menu > programs and get to them just fine but why did they not make it to the setting menus ??
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Imperium:
I am so confused.. im trying to follow the wiki of cooking my first ROM. and at step 4it states: "Extract the OEM Package folder included within the ROM thread to \kaiserkitchen\packages"

What do you mean with this? i cant figure it out..

ps: where is the search thread button???
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] overhaulengines:
oem package

just read this link, scroll down a bit and he states that he removed them, but does not state why:confused::(

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

if you have an email address, i have these packages, V 5.1 fixed (2 parts), i have had no problems with them, but he might be updating them, i dont know. email me and i will email them to you:)

lupe@aircraftoverhauls.com

good luck

Lupe
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] celtickuja:
The OEM packages seem to have been taken down temporarily for some revisions:

EDIT: After seven hours, two replies within two minutes. You just beat me, overhaulengines. =P BTW, I'll be emailing you for them as well, if you wouldn't mind. =)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] overhaulengines:
oem packages

there on the way:D

large files, might take a little while, :eek:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] stainlesspc:
Duuuuuhhhh

Ok I am a big idiot some times :)

Guess that is what I get for staying up till 2:00am and cooking when I should be in bed.

I looked but aparently did not look for the right thing.

Thanks THOMASSSTER

Now that we have figured out i can not ask questions at 2:00am

What would cause my rom to show "D 1.60.00.00" on the first splash screen when Device Info shows 3.02.405.0

Also what controls the "ROM date:" I put a date in when I picked my packages and pressed the change button adn got a changed confirmation box.

Thanks all

Plus a big thanks to Alex, who without his kitchen and instructions I would not be bugging you now, but just downloading someone elses ROM :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
You changed your OEM & SYS folders, but you still have an old ROM folder is my guess... Clean out your kitchen entirely and start from scratch.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Been really busy, sorry... sometime this week...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] cagdas:
:rolleyes: I am so excited, can’t wait to try my first cook, I still did not receive my tilt but I start getting my hands dirty in my kitchen. Now I need to find someone to try my first meal I hope I won’t poison it. Alex Hope you can find some time to upload those packages for us soon. I want to thank you and all the others for your great work and time. I wish I had enough to donate. May be some time when I get a real job.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] thomassster:
to be honest, yea, i just edited that package and used the same UUID. I was trying a bunch of stuff to get it to work. I posted the fix to help one person out. Didn't think it would be the official fix. I also figure, why use the disable beam when there is no beam on the kaiser. Just create your own UUID for the fix and copy paste the registry in.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] overhaulengines:
thanks alex

thanks for your work, i look forward to all your hard work and wait for every update you post. donation on the way.

thanks

Lupe
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
My intent with these tutorials was not to allow anyone who can follow instructions to create a ROM for the public. It was to allow anyone to make their own private ROM and facilitate a community aspect with everyone else assisting each other for cooking and ingredients. Instead, I've seen quite a few people that release their own ROMs with their own OEM packages and fixes, without contributing back to the community.

Because of this, I'm going to be holding off on public cooking kit and OEM package content updates. Public changes will be made to make cooking easier, but new or fixed content will not be added until we see some changes from those releasing publicly w/o contributing back.

Alex.v5.1.OEM.Packages.fixed.again.part1.rar and part2.rar are uploaded to MegaUpload and RapidShare. The only change from the previous version is the removal of Microsoft Voice Command by moderator request.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] marm0lade:
I am confused on what you mean by "contributing back". While its true I have seen a lot of new ROMS (especially 6.1 ROMs), all the new chefs seem to be helpful and give thanks to those who made their cooking possible. Are you speaking of monetary "contributions"?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] MobilePhoneUser:
I also am not understanding what you mean by "contributing back to the community". Isn't releasing ROMS with OEM packages and fixes a contribution to the community or am I missing something?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
You cannot easily extract OEM packages from existing ROMs. It sometimes takes quite a bit of time and technical knowledge to extract an OEM package from a ROM.

Therefore, the people that are using these kits to put forth public ROMs are *NOT* contributing back to the original intent of my tutorials and cooking kits, which is private cooking made simple and available to all.