DogGuy's Kitchen (Now with working BT base)
 

Welcome to DogGuy's Quitch Yer Bitchin' Kitchen (Prettier Edition) 0.6 ... Now with Working BT base!

Straight from the ReadMe.doc --- Let's begin with the disclaimers.

This is NOT the Official Kitchen!
This is NOT the Official Kitchen!
This is NOT the Official Kitchen!

This Kitchen may royally Bork your phone!

Use at your own risk! Neither I, nor anyone in anyway associated with this Kitchen will take responsibility for anything you do with your personal device. Again, Use At Your Own Risk!

This is a ready-to-use basic kitchen based on the scripts in my original Command-Line Kitchen, with a hybrid ROM that took a good team quite a few hours to piece together. Hopefully BT is functional, limited to no disconnects, and good quality. My goal is to show everyone how far you can take the scripts I posted in the Kitchen Maker previously.

The process is simple. Add your OEMs to the OEM directory. Run BuildOS.exe and pick what you want or don’t want included. Run BuildIt.bat. Go to the RUU directory and run RomUpdateUtility.exe.

A handful of OEMs are already included. Namely, some performance and convenience based regedits, and a handful of games and apps. Just the tip of the iceberg though folks, so get cooking! Please remember, this is not the Official Kitchen, therefore there is no error checking or protections to prevent you from removing something important. Use at your own risk!

The end. Questions, comments, concerns, needs or wants, send ‘em my way via PM or in the chat. Best of luck!


Credits:

A big thanks to the dev team for this beautiful rom. DogGuy, Jtrag, Sonny, No2Chem, diiishe … you guys rock!

Tadzio and Bepe and tiermann deserve the highest credits for creating fantastic tools.

ImCokeMan, sfaure3 and dcd also deserve a world of thanks for putting up with a complete PPC newbie and helping me on my path to kitchen-dom.

A thanks to Wideawake. His excellent efforts in breaking down the steps for the Apache were instrumental in understanding the similarities with the 6800. And of course his forum.

Finally, thanks to the entire PPCGeeks community. You guys rock. I would never have even begun messing around with my Mogul if it weren’t for you



--- To download, go to the ftp, Titan\Users\DogGuy\ and download the DogGuys Kitchen with BT base.rar.



Enjoy!



- DogGuy

IM NOT WORTHY!!! IM NOT WORTHY !!!!

thank ya doggie =)

Very nice work DogGuy. This should be very helpful to the community.

"Yes, yes... and a very special thank you to... me!"

heh, just messin with ya

hey dogguy, what "performance" tweaks did u throw in to the base rom?

I believe DogGuys kitchen includes the same exact reg tweaks that were put into the ROM posted for BT fixes. Simple things, title bar, glyph cache, btad2p quality.

The kitchen, though, allows users to pick and choose which of these they want pre-loaded onto the phone.

Nice work. Thanks very much. This device is finally starting to rock.

Do we need to do anything special to OEMs for the Mogul, or can I copy over my Apache OEM folder?

Thanks for all the hard work guys.

You rock. I can't 'til I've got the time to try this out.

Made a custom ROM this morning and it was very smooth. I have run into one issue though though that I also experienced with no2chem's alpha 3 ROM. My phone will go into roaming randomly at work and open up my messaging app. I am not sure what causes this, but I haven't experienced it with Colonel's builds. I used the 1.40 radio on all of these. My signal is pretty decent so I am not sure what causes it.

Anyone else run into this?

don't forget, dogguy's kitchen requires the latest .net Compact Framework to be installed.
Personally, I don't have admin rights on the pc I'm using at the moment, so I can't install .net- but I stand behind dogguy knowing his kitchen is most likely the shizzle. Will have a go at it later...

To answer my own question, looks like older OEMs can be used. :-)

Just got done running this and flashing. If this isn't the official kitchen, it damn well should be.

Christmas come early...damn I love this place!

Thank you to all involved with this. Your hard work and effort does not go unnoticed!

Yes, most WM6 OEMs should function just fine with this incarnation of the kitchen.

As for it being official... heh, its not even in the same league. If you've seen the Apache kitchen, then you have an idea of just how much development is going into making the "official" kitchen a really impressive piece of software.

My intent in releasing this kitchen, with this particular base rom, is so that we will hopefully have a large group to draw conclusions from about the rom. By allowing people to customize this beta rom (and it definitely is a beta, not a final release) we'll be able to pull real world data from a *lot* of users, and hopefully lock down any remaining issues or bugs that didn't show up in testing. Doing this will give us a good idea of whether or not this base will be suitable for adapting to the real kitchen. I'm just trying to make sure only the best of the best gets passed testing and into the official release.

With that said, I'm very glad to see such a positive response. I encourage everyone to test hard, and post about any successes or errors involved with the process. I'm sure there are bugs remaining, so the more info we get, the faster we can fix 'em!

Happy cooking,
- DogGuy

Haven't had anyone experience this in testing, but I'll certainly be trying to recreate it.

What programs did you cook into the rom, and did you use the same ones with no2chem's alpha 3?

- DogGuy

oh my.. can't wait to go home and try this out... I wonder how clean is the rom included in this kitchen... looking forward to it!! Once again, thank you DogGuy with all the helps you provided me be4.

Just to clarify a few things:

I've never built a ROM before. I didn't have a 6700, so the Mogul is my introduction to this world. In order for me to "cook" an application into this, I need to use that OEMizer application to turn a CAB installer into an OEM, and then place it in the OEM directory, correct? That program seems relatively self-explanatory, but is there anything I should be careful to look out for?

EDIT: Argh! I was all ready to do this, and then I noticed I left my memory card in the card reader at home, and it has all my installers on it. *sigh*

Quick question: is there MMS bundled in this ROM somewhere that I'm not seeing? Whenever I try to add an ArcSoft OEM, I get errors about duplicate files. Example: I get an error that AudioStrmReader.dll already exists in the dump directory, but when I do a search in the kitchen directory for that file, it only finds the one in the OEM directory.

By the way, many thanks to everybody who made this possible!

Here are the extra things I cooked in and I did cook most of them on the no2chem ROM I had the issues with before. I wasn't sure if it was something related to the base ROM making it go into roam like that since I didn't see it on Colonel's.

Advanced Configuration
Hidden-Office-Requirements
HTC Action Screen
HTC Duo Album
HTC Home 2.0.814.722 Color
HTC Voice Recorder
Kevtris
Ms. Pacman
MusicID
Null Keyboard
Office-Excel
Office-Powerpoint
Office-Word
Oxios Memory
PIEPlus
QuickMenu
SIPChange
ThreadedSMS
TierAutoinstall
Total Commander
VistaHide Battery Gauge

I am very new to this...should I choose a custom ROM first then do this kitchen or what's the order I should go in?

First, read about unlocking the Titan and what you need to to in order to flash.

Second, I would read about the kitchen and how it works before you start making stuff in it. Custom ROMS are just that...custom based on what the ROM builder wants in the ROM. The kitchen is nice because it turns you into the ROM builder...so you can make it anyway you like it!

While most, and indeed all of, these will "build into" the rom, I'd like to remind everyone that this kitchen is not yet "inter-mingled" with a set of OEM's. The PPCGEEKS version "that will be more official" is still held up because to make a good rom-kitchen one has to make sure that the operating system and OEM addons are "interrelated" well so that they dont stomp on new application installs.

Dumping a lot of stuff into this ROM one needs to understand that they may well be upsetting the delicate balances that were achived to get this out.

That said, you're experiences are and will be noted, using this, sos we can get the proper balance into the "official kitchens". But as DogGuy said at the start of this, you can def come up with combinations that will bork you're device rather seriously, so be careful, we're still tuning the SYS and OEM dirs on this to make it a more "official" type o kitchen.

Thanks a bunch, if nothing else it makes for some interesting reading. Anyone else notice the GPSID module and how it exports GPS and COM port functions? Always a good read. :-)

Hi, is somebody know wath is the password for extracting the Registry bckup app, in the same folder on the ftp. And is it a too great work for a newbee to make it all work on a telus branded device... If, i'll probably wait for an official Kitchen. But for now in a learning meaning is it possible to test ROM on an device emulator for PC, to don't take a risk of bricking device... Learning with a less risk factor lol As a newbee i'm not confient enough to test my first attempt on my preffered toy.
thank for you're answer

I think the password is "PPCGeeks" (without the qutoes).

hey DogGuy....thanks for the kitchen....so far its working great....the only thing as of now that im having trouble with is the personal oemizer.....its like its partially working, i cant get the email and mail2web settings to show up once i flash my phone. I entered the data into the program, saved it and hit create oem, and then built the os and flashed my phone but i dont see the email already setup. I know some parts of the personal oem is working cause i see my owner's information other things i changed making it to the phone.....any help is great;y appreciated......
________
ALICIAKISSME LIVE

Same here. It would bring up ActiveSync and freeze the device, for me.

LOL....u got farther then me....i dont have anything listed there....hopefully someone will be able to help us out
________
Foxypoison69

Mine does it with the stock Sprint rom. It starts doing it after I load the threaded SMS cab file.

Well, I just got done trying to build my first one (a bunch of my CABs won't work, and some of the OEMs I created tell me such-and-such file already exists, so I had to turn off a few), and I got this error: Error building default.hv and user.hv!

Help?

Anyone get a 10 Button Comm Manager OEM to work in the kitchen? I've been trying but to no avail...

Wich OS revision is this kitchen (core)

Sprint is default at 2.09
Alltel I believe is 2.16

Kitchen is ... ?

Kitchen is 2.09.

None of the above. Sprint is 2.09 and 2.16, Alltel is 2.14, Qwest is 2.13.

This one is partly 2.09(most of OEM), partly HTC Universal's 5.2.1933 Build 18533 aku 0.7.0 (SYS) with the XIP port from No2Chem.

- DogGuy

One of the things in the works ATM is completely separating out packages such as the Comm Manager, Dialer, most of OEMApps in general.

The biggest fault of bepe's BuildOS (which guru's great new version addresses) is that it automatically fails with duplicate files. Compare your Comm Manager OEM's contents with anything already in the \OEM directory and before running BuildOS remove all of the matches. Then run BuildOS and watch for any errors. Check the log.txt in the temp directory when it completes to verify there were no major registry errors, etc.

- DogGuy

alex_electro: The registry backup on the ftp is just a dump for comparing notes on a possible BT volume increase hack. Not needed for the public. It was however made with dotFred's Task Manager (great program) and I highly recommend adding that OEM to your builds. :)

elosogrande7076: Tiermann hasn't been around in a couple days, but it appears there are a couple bugs in his implementation of adding mail2web to OEMizer. Keep an eye on the Personal OEMizer Thread for any new developments.

TurboFool: Whenever encoutering a registry error (building *.hv) you need to go into the \temp\ directory that gets created by BuildOS and read the log.txt. Around the bottom you will see an error explaining which .rgu failed, and at what line. Open up the OEM that is the culprit, and examine the .rgu for any syntax errors. OEMizer is good, but not perfect. Occasionally path's are parsed incorrectly, etc etc.

stroths & digiblur: I'm taking a stab in the dark that it is the threaded SMS app. That is the one thing listed that I haven't tested against and I definitely have not seen the issue recreated. Try pulling that app and seeing if the problem persists. Please let me know the details.

To everyone else: Keep an eye out for updates to the kitchen. I have a revision that is slightly more memory efficient, and hopefully (if I can get some work done before heading out of town tomorrow) will have some of the OEMApps separated out proprely. Also have a fun touch-based custom rom in the works, of course created with this kitchen, to showcase what all can be done with both the rom and the kitchen. Good stuff in the works, so keep on cooking and giving me bug reports. And a side note: No2Chem has released his newest rom in base format. Feel free to test it out with this version of the kitchen.

Happy cooking,
- DogGuy

Excellent. I'm playing around with it at the moment. Thanks for the suggestion.


I echo everyone here by saying thank you for your hard work and we wait with bated breathe on this! Keep up the great work and thanks a million!

I am very excited about this, and just a note, dont be in a hurry to get away from buildOS, call me oldskool but i prefer the older kitchen method highly over the new one for several reasons but thats another thread all togethor.

If you are breaking out the OEMAPPS into folders, would you mind including the default original wm6 dialer, even as a "false" checked OEM. Im a huge fan and my own efforts in removing the touch dialer keep giving me a blank dialer LoL. Anyways just wanted to thank you for getting me back into a kitchen especially since my 6700 took a shit on me a few days ago.

Thanks! and keep up the great work.

Help PLease!!!!!
 

I Flashed my mogul with custom rom before but when i tryied the kitchen it flashed it but now its stuck in the sprint logo screen. can someone please help me!!!!!

nevermind!!!
 

just to explain maybe for a newb that already unlocked there phone and flashed with a custom rom. i basically did a bad flash because cause it still don't under the oemizer and the whole process but if you get stuck in the sprint yellow screen with no OS boot. PRess POWER+CAMERA+OK button+ SOFT RESET and you will enter bootloader mode and do a new flash. I THOUGHT I BRICKED MY MOGUL FOR A GOOD HOUR!!!


PS. Oh ive been on ppcgeeks for a good minute, but i'm not a poster type of guy all like that. but i wanna thank every man,women, or user on this site for the information you guys passed and thought other people like me.. THANKS ALOT!!!!!!!!!