Okay I have flashed my telus titan many times using the usb method and the flash card method (prefered) now I would like to learn the kitchen method, which I understand I can modify to include the programs I have to load after I do the flash. I get the buildnb and then selecting the programs I like, what I would like to know is if I want to add my tomtom 7 to the build is this possible. plus some other games that I have. What folder to I add these files to? If there is already a discussion about this could you send me a link.
Cheers
I'm not sure how buildnb works, but I'm more familiar with BuildOS from ppckitchen.org and with that, all you do is copy the stuff you find into a folder and BuildOS loads it in as part of it's stuff you can pick from. I would give it a try and see if it's better/worse/indifferent for you. And the guys at ppcgeeks.com are always posting stuff about the kitchen and custom roms. I don't see much here about the kitchen, it's mostly about custom roms.
jc, the kitchen is quite easy to use. But you cannot just dump programs into it and have them available to select from buildnb. The programs that you have will most likely be in the form of a cab. For use in a kitchen the programs need to be in the form of an OEM. There are tools available to OEMize a cab. Just do a search here and you wiull find the tools you need. Then just dump the OEMs into the existing OEM folder inside the kitchen and then when you run the kitchen the programs will be there for you to select. They will install with the ROM, not after it.
You do have other options if you dont want to OEMize your cabs. You can search for Alex's OEMs at ppcgeeks. There are hundreds of premade OEMs for you to select from.
Another alternative is to keep your cabs and just use UC to automatically install them immediately after you install your new rom. This is the preferred method for most of us now as it leads to less problems and allows for programs to be uninstalled at a later date which OEMs will not allow.
Sleuth255 has an excellent tutorial about how to automatically install all your favorite cabs using UC. Search for it and you wont go wrong.
All you need to do is find OEM packages for the programs you want. If you use DCD's kitchen just add them to the OEM folder. If you use PPC Kitchen just add them to the User OEM folder. Then just select them once you run Build OS.
I'm not sure how buildnb works, but I'm more familiar with BuildOS from ppckitchen.org and with that, all you do is copy the stuff you find into a folder and BuildOS loads it in as part of it's stuff you can pick from. I would give it a try and see if it's better/worse/indifferent for you. And the guys at ppcgeeks.com are always posting stuff about the kitchen and custom roms. I don't see much here about the kitchen, it's mostly about custom roms.
Click to expand...
Click to collapse
Hate to break it to you, but this uses BuildOS too, just a different version. Buildnb is just a batch file that g'reloc's and calls BuildOS among other things after BuildOS is run.
I'm trying to learn this stuff too.
Here's some of the stuff that I've found:
OEM Tutorial Thread:
http://forum.xda-developers.com/showthread.php?t=347361
there's more links at the bottom of the 1st post in the thread
Here's the link to packages - say for Kaiser - So I don't know if they can be used on Titan? Anyone knowledgeable please chime in.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_software_recs
??? All the links on Alex's thread seem to be Kaiser based - how much of this is applicable to the Titan and/or other devices?
I agree that ppcgeeks is a good resource too.
DCD's kitchens seems to be fairly easy to do a build. I'm still learning what I want, which versions to include, what everything that's there does, etc...
In theory it seems simple, I'm not finding the learning curve to be all that easy though. A lot of trial and error. But that's part of the challenge, I suppose.
It would be nice if the people with a lot of experience would chime in with tips, links, and comments that would help gather the information into one place for those of us that are learning - maybe I need to go hunt through the wiki's some more, IDK. But sometimes it seems the more threads I read the more confused I get.
My opinion to all of you...and again..this is just MY opinion...take it or leave it...
Build the rom using the kitchen as is with no added personal OEM's. Install all programs/applications/tweaks after flashing either manually, or much easier by UC.
I've converted a few so far, and they haven't turned back. OEM's can be so messy, and can be a HUGE pain in the ass if you need to uninstall/troubleshoot any problems.
My advice would be to read the entire thread on UC, as well as the threads in the Titan Upgrading forum pertaining to UC (I know I've talked about it quite a bit, as well as many others).
Sound good to me. I'm not one who likes to reinvent the wheel if I don't have to, but I am willing to go through a little extra pain to get what I want. If I can get the same results through UC vs. OEM'ing CABs, I'm game. The OEM'ing of CABs so far for me has been a real pain in the arse.
I will do some more reading on UC since I haven't totally gotten the results from that yet that I want. I'm sure my minor problem with the UC cfg file is not unique.
What about adding some of the nueTools into the DCD roms? Reading the text in the included files - some of them can only be rom'd like the ext'd rom utility. Looking that over, I haven't figured out, with any reasonable confidence, how to add this to DCD's roms. I have searched some, but not extensively on this one yet.
Related
I have a lot of OEM progs how can I install them on my phone?
OEMS are used in kitchens there is no way to just install them that way they either need to be Cab files or used in a kitchen
If yourusing a kitchen, you just drag and drop them into the OEM file. It's not always that easy though, as it might not interact well with your build. Most of these guy's put countless hours into these before a kitchen is released. If you know enough, or do enough searching you can incorperate it yourself. do a search on building it the old way. Good luck , and be prepared to rebuild it countless times to get it right.
DCD if you dont like what im doing just tell me to delete this post and i will.
All credit goes to DCD one of the best kitchen and Rom maker's out there.
If it wasn't for him our 6800's would be almost useless.
This is for the people who are using the titan kitchen. I took DCD's latest build and repackaged it for the PPCKitchen.org Titan Kitchen located
here http://forum.ppcgeeks.com/showthread.php?t=23206
Place it in your BuildOS/Kitchens directory and then extract "Titan_DCD_3.01_Selections.txt" and place it in the BuildOS/Projects directory.
Now you can create your own custom DCD rom using the new kitchen and DCD's latest build.
I've been using this for about 20 hrs and the rom is very stable.
Thanks again DCD u Da MAN!!!!!!!!
Make Sure to remove---> _fixed <---from the end of the file before u place it in the kitchens folder.
Download
http://rapidshare.com/files/108106961/Titan_DCD_3.0.4_FIXED.rar REALLY FIXED this time LOL
thank i'm looking for this. I ran into error error nk.dat
AstronusX said:
thank i'm looking for this. I ran into error error nk.dat
Click to expand...
Click to collapse
Sorry i forgot to change it from os.paylod to nk.fat, im up loading a fix right now thanks.
Errors in PPCkitchen
King - Thanks for putting this together
Unfortunately, I'm getting an error message (a bunch).
I downloaded the main file and did the updater.
When I go into BuildOS and select DCD 3.0.4 5054 or 5060, I am bombarded with error messages "Internal Error - Option.xml GUID not found (PROGRAM - xxxxxxxxxxxxxxxxxxxxx) where the "Program" is the name of the program and the x's are registry keys.
After I click ok 100 times to get through to the Kitchen, it allows me to select programs and build the OS, but once I install it, nothing actually gets installed on the phone.
Do you know what is causing this? Any help would be appreciated.
Thanks,
mfrish said:
King - Thanks for putting this together
Unfortunately, I'm getting an error message (a bunch).
I downloaded the main file and did the updater.
When I go into BuildOS and select DCD 3.0.4 5054 or 5060, I am bombarded with error messages "Internal Error - Option.xml GUID not found (PROGRAM - xxxxxxxxxxxxxxxxxxxxx) where the "Program" is the name of the program and the x's are registry keys.
After I click ok 100 times to get through to the Kitchen, it allows me to select programs and build the OS, but once I install it, nothing actually gets installed on the phone.
Do you know what is causing this? Any help would be appreciated.
Thanks,
Click to expand...
Click to collapse
Is this your first time using the kitchen?
King_tee - I had to do alot of editing to get ALL the errors to go away. I had to remove the welcomehead96.png, also had to remove a few other items.... like remotedesktop..... I guess I should have taken a log of what I did....
Edit - However - VERY nice job getting it to where it is..... Thank you
Thanks will try. The BuildOS in the regular kitchen is crashing so I can now cook a kitchen.
Also will my OEMs made for the 3.0.1 rom work if I put them in the build os directory. I didn't use the OEMizer w/ BuildOS. It appears to be the same just w/ a different save directory.
azclown said:
King_tee - I had to do alot of editing to get ALL the errors to go away. I had to remove the welcomehead96.png, also had to remove a few other items.... like remotedesktop..... I guess I should have taken a log of what I did....
Edit - However - VERY nice job getting it to where it is..... Thank you
Click to expand...
Click to collapse
No prob az i forgot about getting rid of those files. I thought i got all of them. I will upload a new file with the fixes for those who haven't downloaded it yet.
NEW FILE UP LOADED
Let me know if its working for you guys
As of this morning, the version I downloaded still gives an error (can't find HTC Sliding Sound module) when trying to load the selections.txt file for the DCD kitchen.
drgreenberg said:
As of this morning, the version I downloaded still gives an error (can't find HTC Sliding Sound module) when trying to load the selections.txt file for the DCD kitchen.
Click to expand...
Click to collapse
The sliding sounds module is in the DCD OEM's folder......when u open it up in the kitchen it should come up as a selectable OEM. At then point all you have to do is select it.
Bell?
Does the kitchen work for Bell phones? It does not seem to be in the carrier list.
jondixon said:
Does the kitchen work for Bell phones? It does not seem to be in the carrier list.
Click to expand...
Click to collapse
I don't know if it does.Are you are referring to the ppckitchen or DCD's Kitchen?
What i have provided is just a modified version of DCD's work (all credit goes to him) that will work in the ppckitchen.
You can check over here http://forum.ppcgeeks.com/showthread.php?t=23206
if you are talking about the ppckitchen, and they should be able to answer your questions.
If you asking about the DCD kitchen you can ask over here http://forum.xda-developers.com/showthread.php?t=385336 and im sure he will help you out.
I guess the obvious question is, what's the difference between the two kitchens?
DCD's kitchen is built around his ROM. The PPCkitchen kitchen isn't designed for any specific ROM or device.
Advantages of DCD's kitchen:
It's what DCD is using, so you know it builds his ROM like he intended it.
Advantages of PPCkitchen's kitchen:
Easy to install.
Prettier front end.
More error checking.
More OEMs to pick from.
Self updating.
Device dependency/exclusions supported
Carrier dependency/exclusions supported
OEM dependency/exclusions supported
Easy to move same configuration from one kitchen to the next.
Effortless switching between ROM configurations and kitchens
Splash/animation support
gguruusa said:
DCD's kitchen is built around his ROM. The PPCkitchen kitchen isn't designed for any specific ROM or device.
Advantages of DCD's kitchen:
It's what DCD is using, so you know it builds his ROM like he intended it.
Advantages of PPCkitchen's kitchen:
Easy to install.
Prettier front end.
More error checking.
More OEMs to pick from.
Self updating.
Device dependency/exclusions supported
Carrier dependency/exclusions supported
OEM dependency/exclusions supported
Easy to move same configuration from one kitchen to the next.
Effortless switching between ROM configurations and kitchens
Splash/animation support
Click to expand...
Click to collapse
I honestly don't think you give DCD enough credit for his work.... Here are some more Advantages....
Easy to use
Builds a basic ROM with only 2 clicks of the mouse.
Can be used behind firewalls.
No IP logging when you use it. (I had been told this was logged with your login name)
In all fairness both systems work very well, while the PPC kitchen has a more elegant streamlined interface, I do believe the end result is the same, a working ROM the way "I" want it.
error
hey guy anybody else getting an error unable to make file
when it goes to unpack the ppcgeeksoem rar
azclown said:
I honestly don't think you give DCD enough credit for his work.... Here are some more Advantages....
Easy to use
Builds a basic ROM with only 2 clicks of the mouse.
Can be used behind firewalls.
No IP logging when you use it. (I had been told this was logged with your login name)
In all fairness both systems work very well, while the PPC kitchen has a more elegant streamlined interface, I do believe the end result is the same, a working ROM the way "I" want it.
Click to expand...
Click to collapse
Could be because DCD has only a little to do with what we're talking about (which I gave him credit for). That's Bepe's buildos you're looking at, and essentially what we're comparing is Bepe's buildos w/ DCD integrated against PPCKitchen's buildos w/ DCD integrated.
You can't seriously suggest that Bepe's buildos is easier to use - the interface is practically identical! Both are about the same difficulty to use in their most basic, unaltered configurations, and both can build a basic rom w/ 2 clicks. Installing, configuring, starting, and maintaining is a lot different however...the nod hands down goes to ppckitchen there. Once you get past a basic configuration, PPCkitchen's buildos is unchallenged.
The proxy/firewall thing is fixed (general release this weekend) and it doesn't log IPs (never has).
Bepe's buildos get's the nod for no internet connection required, and the previous version (I don't know about v2) get's the nod for Linux compatible. Bepe's buildos also get's the nod for being more interfaceable to other projects and having more projects using it, but none of that is related to the original question (except maybe linux compatibility). [EDIT: v2 isn't native linux compatible, so no nod there.]
All of this is not too suprising, as PPCkitchen's buildos is, at it's core, an evolution of Bepe's Buildos.
I give credit to all sources DCD's kitchen / PPC Geeks kitchen and more.
They both offer the tools to make a ROM to your likings, some better then other, but the fact of the matter is that it gets the job done.
What PPC Geeks version is doing is making a bit more user friendly ( in my opinion ), but I still used DCD's kitchens because I really don't add any extra OEM's to my ROM's unless it is a specifically Themed ROM and then again I can get it done with both kitchens with ease.
I guess users will just have to test them both out themselves to see if they prefer one or the other.
What would be great is if we can have a Modifier / virtual simulator / kitchen where we can find ways to modify our ROM's / PPC's to their best potential ( such as drivers, RAM Management that works / compatibility with different OS and maybe interface change support ).
A virtual simulator to test out all of our modifications by simulating our respective device just as if we were to cook the ROM ( this could save tons of time rather then just flashing all the time or preventing an accidental bricking of your phone)
And a Universal kitchen for practically any Device ( well TITAN at least for our use ) that works on XP, Vista, MAC, and even Linux.
Im sure with all the developers on this forum and on ppcgeeks we would be able to get this done some time in the future.
Just an Idea....
[email protected]$ said:
What would be great is if we can have a Modifier / virtual simulator / kitchen where we can find ways to modify our ROM's / PPC's to their best potential ( such as drivers, RAM Management that works / compatibility with different OS and maybe interface change support ).
A virtual simulator to test out all of our modifications by simulating our respective device just as if we were to cook the ROM ( this could save tons of time rather then just flashing all the time or preventing an accidental bricking of your phone)
And a Universal kitchen for practically any Device ( well TITAN at least for our use ) that works on XP, Vista, MAC, and even Linux.
Click to expand...
Click to collapse
PPCkitchen buildos is actually the closest you can come currently for easily swapping components around, and there's a universal kitchen here on xda that supports many devices (way more devices than PPCkitchen does).
Don't hold your breath on the hardware emulator
lightbiter said:
hey guy anybody else getting an error unable to make file
when it goes to unpack the ppcgeeksoem rar
Click to expand...
Click to collapse
You'll have to elaborate a little better. If I had to guess, however, I'd say that you might have an older version of winrar installed. As a workaround, you can manually extract and modify the selections to use the extracted dir instead of the .rar.
how can i modify registry keys such as htccpl in any rom kitchen? possible at all? or are they always related to the htccpl.cpl in the windows folder? how to modify that one then?
i just can't modify or delete them in neokit.
cheers.
chriskay said:
how can i modify registry keys such as htccpl in any rom kitchen? possible at all? or are they always related to the htccpl.cpl in the windows folder? how to modify that one then?
i just can't modify or delete them in neokit.
cheers.
Click to expand...
Click to collapse
Some in reg, some in provxml Check your PM for more detail, friend !
yeah, thanks, mate! i found all entries i need in those provxml files! great stuff!!
now i am almost done with all modifications reverting everything back to "original".
any ideas how to change "hidden" status of a single file? i want to make the templates for notes and office visible.
cheers!
chriskay said:
yeah, thanks, mate! i found all entries i need in those provxml files! great stuff!!
now i am almost done with all modifications reverting everything back to "original".
any ideas how to change "hidden" status of a single file? i want to make the templates for notes and office visible.
cheers!
Click to expand...
Click to collapse
I'm not sure what you are talking about, but I do like the word "original".... If you are done, is it worth sharing?
well, as i stated in cloudyfa's thread, i am not a friend of too heavily customized roms even though most of them look pretty cool. everyone is individual and has a different taste. therefore i really liked korand's contribution. unfortunately there were still some minor flaws, such as an incorrect wm6 sound scheme (as i believe), which i could not figure out to fix.
but with cloudyfa's rom providing wpa2 and showing no signs of bugs so far, i just could not resist making my own close-to-originally-offical wm6.1 rom, because no-one seemed to respond to my appeal of making a truely clean version. so i took the challenge myself... and it was quite some lesson and a lot of fun, however, i still do not consider myself a rom cook (yet).
and "yes", i will share it if cloudyfa does not mind and if i will not encounter any problems while testing my "creation" at the moment. i only need to figure something out about user customization. maybe you have an idea since i could not find anything specific on my question:
if uc is enabled, will it still be possible to run autorun from extended rom even though it would be redundant? because there is still the registry key set for autorun destination on extended rom. or can i delete it? or should i leave it for some kind of "dual autorun mode" ?
cheerio.
chriskay said:
well, as i stated in cloudyfa's thread, i am not a friend of too heavily customized roms even though most of them look pretty cool. everyone is individual and has a different taste. therefore i really liked korand's contribution. unfortunately there were still some minor flaws, such as an incorrect wm6 sound scheme (as i believe), which i could not figure out to fix.
but with cloudyfa's rom providing wpa2 and showing no signs of bugs so far, i just could not resist making my own close-to-originally-offical wm6.1 rom, because no-one seemed to respond to my appeal of making a truely clean version. so i took the challenge myself... and it was quite some lesson and a lot of fun, however, i still do not consider myself a rom cook (yet).
and "yes", i will share it if cloudyda does not mind and if i will not encounter any problems while testing my "creation" at the moment. i only need to figure something out about user customization. maybe you have an idea since i could not find anything specific on my question:
if uc is enabled, will it still be possible to run autorun from extended rom even though it would be redundant? because there is still the registry key set for autorun destination on extended rom. or can i delete it? or should i leave it for some kind of "dual autorun mode" ?
cheerio.
Click to expand...
Click to collapse
yups, you can still run some application from extende rom.
At windows folder, you will find config.txt . You have to give some command on it.
The command there, is just a RST ( Reset ) . But If you give a command first, it will install some cabs. It all command from AutoRun
This is some command
LOCK: Enable
CAB: \Extended_ROM\TCPMP.CAB
CAB: \Extended_ROM\Cabs\ABCD.CAB
LOCK: Disabled
RST: Reset
the command will install TCPMP.cab and ABCD.cab
share at XDA is always a good one.
With Cloudyfas ROM, there is a provxml file that sets the keys for AutoRun to somewhere in the windows directory. You will have to remove/alter that for autorun from the storage card.
The point of AutoRun is to allow you to install cabs etc before the user can really use the ROM. UC is to provide users with a faster way to set up the ROM. The two can and should co exist.
so if i got it correctly: putting the common command lines of the extended rom autorun PLUS the command lines of sdautorun into this single config.txt file would make the device boot and install from both locations one by one?
so, what are your recommendations about the registry key:
[HKEY_LOCAL_MACHINE\Comm]
"TurnRadioFlag"=dword:0
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"
leave it or kill it??
edit: decided to remove it due to its complete redundancy. it is uc already... now i am close to finishing.
edited edit: put it back in. i think it won't hurt and maybe someone still needs it.
cheerio.
One of Cloudyfas ProvXML files overwrites that, so it is completely redundant!
It's called mxipupdate_zz_oemoperators_102_CheckAutorun.provxml
You can look at it and see what it does.
The two AutoRun files (SDConfig.txt and Config.txt) are separate files that run independently. The point of UC is User Customization. All you need to do is make sure SDAutoRun.exe is in \Windows and that the last line of your config.txt file is
Code:
EXEC:\Windows\SDAutoRun.exe
That is all that is needed for it to run.
ok. removed the redundant entries. i was just thinking there might be some way of a "dual boot". but actually this is rubbish. so i leave it as uc as it is.
The point of UC is that the two are seperate. Everything can be achieved with just one of the two systems, but with UC, you (the chef) can install cabs, and the user can install tweaks etc.
I'm currently running DCD 3.0.1, and looking to upgrade to 3.2.2, so I'm trying to figure out whether to use UC or OEM to install my apps. I've read through lots and lots of threads related to both UC & OEM, but can't find any definitive answer as to which is the better method. I would imagine it depends, but depends on what?
From what I can come up with:
UC - pro - easy to change without having to rebuild the ROM
UC - con - need to have SD card in (yes, a minor con, but I had to write something)
OEM - pro - get back to your "optimal" setting quickly - doesn't require installation of apps
OEM - con - need to rebuild ROM to make any change, whether large or small, then reflash
note: I did try searching, so I apologize if there is a post/thread explaining this...
I think that you having a hard time finding a con for UC shows that it is the strongest most stable solution.
OEM is good for some things and installs those things a bit quicker being that they are included in the ROM. UC is a bit slow, but I know that if my sdconfig.txt file is written right things happen the way they should. It is also always there on your card when you need it. This way you can flash everything from your phone without ever needing to connect to the PC (if you have wifi or data plan).
Use UC and post your sdconfig.txt file for us to review if you need more information. Learn more here.
UC is better.
What happens when your favorite program gets updated? With cab installs, you can just overwrite the older cab.
Also, with OEM's, yes you don't have to install anything after the flash, but the more OEM's you include in the ROM, the bigger the ROM. It'll take longer to flash than a clean ROM.
If you don't know what you're doing with OEM's and initflash files, you could also end up with a crap ton of bloat in \Windows bogging down the device even further.
Once UC is setup, and your config file is written, it's very easy to make simple changes to the config. In the long run, it's much more clean, efficient, and easier to maintain.
Looks like I'll be going to UC route, then...thanks for the replies.
(and I've had Sleuth's UC thread bookmarked since he posted it )
I have tried making some OEMs myself from Cabs (with some success).
I was wondering 2 things.
Does anyone know of anywhere that OEMs are downloadable. I am looking for programs like:
S2P
S2V
S2U2
TouchFlo
iContact
LiveSearch
Opera Mini
Mortscript
Weather Panel
Today Agenda
UL
I am thinking that my problems stem from the final stage
"The next window that appears, known as the 'initflashfiles tab' is for executable and help file links. Select which files you want your links and the folders to place them. Select and apply for each link and when finished, click done to proceed."
Can anyone explain this a little clearer? Do I actually have to do anything in this screen? I would love to be able to cook my own ROMS to make it easier to get my phone where I want it after a hard reset.
Also does anyone know if you can alter the OEMs and cook them. For example, could I replace the default themes in Weather Panel with the Diamond ones so that I do not have to copy from the card when resetting?
Sorry for all the questions but I recently did my first flash and now have the bug and it takes me ages to install everything every time i do it.
I get all mines from ppcgeeks some work with dcd some don't.
I use the UC option in the kitchen and use the OEMizer to create the info for it to install the CABs you want. They must be on your SD Card but it works great. It will also copy files from the SD Card to Main Memory as well. It is supposed to be able to make registry changes to but I never got that to work with just editing the provisional.xml file. OEMizer is great for several settings any ways and you will have your own personal OEM to put in the kitchen to bake.
PPC GEEKS oem.rar for the easy out way or if you are into learnning any of it oemizer works pretty good to.
I have use some on this post.
He does take request.
http://forum.ppcgeeks.com/showthread.php?t=25696
Wow, thanks for that last one, I will post some of my requests on there as well. Can't wait to get cooking!
Here are some I have made......