Develop Bugs

noob question: kitchen vs tools..same?

Newbie question. I don't understand, what is difference between a kitchen and tools like mamaich's ? At first I thought they were the same but now I'm not sure because I keep seeing references that don't make sense.

Post removed.

Post removed? That's it? Pardon me....Look, I know this is a newbie question but I am honestly confused as to what the definition of kitchen is. If I use mamaich's tools to prepare, view, etc. I end up with what seems, to me, to be a similar thing as a kitchen. Are they the same? Is there something about a "kitchen" that is fundamentally different than only using the tools? I have read many, many pages here and I'm honestly trying to understand. Please point me in the right direction. Thank you.
edit: sorry, I thought "post removed" in the earlier post meant I got my message removed from the forum by an admin, anyway, my question still stands.

Since the unhelpful member above failed to give you a decent answer, I will help you. Tools are either a program or a set of programs designed to do a task with the roms (for example, Mammich's tools are designed to help you edit the imgfs part of the rom). A kitchen is a set of tools (made by various people) designed to edit the whole rom or most of the rom and build your own custom roms.For future reference, if you ever have any other questions about rom building, let me know and I will help you out as much as I can.

Thank you very much Steven855 and I appreciate the offer to help.

I originally gave an inadequate answer - thus the removed post. Home ill with the flu, Nyquilled up and forgot which section I was in (thought I was in the Kaiser specific section and gave an answer associated with that). No ill intentions, so to speak.
What I will say is the various tools are something a newbie should probably feel comfortable using. Before using a kitchen, read, learn and flash a number of others' custom ROMs. While the great developers here have made cooking custom ROMs very easy with the kitchens, you can cause a lot of problems with your device if you don't know what you're doing.

No ill intentions taken. Like I said, at first I misunderstood and thought my post got nixed by an admin. btw notwithstanding Steven855's helpful answer, I had my question answered earlier on another thread when the same question came up.
Quote originally Posted by ramsses:
My understanding is the kitchen implies each module (with its associated registry - RGU - files and dlls etc.) is explicitly separated so it can be incrementally and selectively combined. What we are doing here is taking an existing set of ROMs and combining the dlls, exe etc. by hand - there isn't a handy gui where you can select which module you want. Also, the registry is necessarily hand crafted too. So by using the extract/rebuild tools, we are making a ROM, but it isn't a kitchen, more a roadside burger van!
Thanks again, really enjoying this site, and learning alot.

Steven855 said:
Since the unhelpful member above failed to give you a decent answer, I will help you. Tools are either a program or a set of programs designed to do a task with the roms (for example, Mammich's tools are designed to help you edit the imgfs part of the rom). A kitchen is a set of tools (made by various people) designed to edit the whole rom or most of the rom and build your own custom roms.For future reference, if you ever have any other questions about rom building, let me know and I will help you out as much as I can.
Click to expand...
Click to collapse
Hi Steven. I was wondering if you knew about ROM cooking for Verizon CDMA devices..ie the i730? I was looking around to see where I would be able to find the bootloader for it but I haven't found any answers yet. Thanks.

Sorry! Unfortunately, I don't know anything about rom cooking for pocket pc phones (yet). I'm still trying to get the hang of this rom building stuff myself (after 2 failed attemps to make an updated rom for the axim X50(mid)).

No order

Hello, guys!
The forum is super but here is ocmplete disorder. Where are the ROMS?
How can one find a ROM file here?? The forum is huge and the search leads to discontinued results (2008 year)
Can someone point me to ROM file archive here?
BR

I'd demand a full refund of the money you've paid....
Seriously, if you scroll down through this list a few pages, some kind person has compiled a thread with all the links in one place. Search is terrible and you have to spend lots of your own time. Still, it's free.

Man its full of ROMs. Most active topics or most discussed ROMs are showed on first page. U dont need to search, just click on thread one the rom u like. Its noted by Cook, Built, WM version, sense version, and ROM Version.
Its easy as it can be.

But it's a mess here!
No normal instructions. All are outdated.
Well, as it was said - it's free and therefore it's messy.
ROMs here - one file, no Ruupdate.exe , no nothing. Like if any user comming here is a professional HTC developer. I am simple user and i am sick of spending hours of my time by gathring info by tips. Well, like i said -- good forum, but no order.

What are you complainin?
Please just have a look at recent posts as already said.
The threads where you have a lot of activity are the threads with new roms.
There are also plenty of tutorials!
For example this one: http://forum.xda-developers.com/showthread.php?t=416211
For sure you will need some time to compare different roms and find your best fitting one....which comes with the big choise of roms.
And also there will be little problems from time to time which I'm sure you can solve in a short amount of time.
I can recommend the google search, not built in forum search.
Concerning flashing you don't need to use Ruupdate.exe, it's way easier to name your .nbh file DIAMIMG.nbh, move it to the phone's internal storage and flash directly (see tutorial)
Kind regards and have fun with your new roms

Shark_XXL said:
What are you complainin?
Please just have a look at recent posts as already said.
The threads where you have a lot of activity are the threads with new roms.
There are also plenty of tutorials!
For example this one: http://forum.xda-developers.com/showthread.php?t=416211
For sure you will need some time to compare different roms and find your best fitting one....which comes with the big choise of roms.
And also there will be little problems from time to time which I'm sure you can solve in a short amount of time.
I can recommend the google search, not built in forum search.
Concerning flashing you don't need to use Ruupdate.exe, it's way easier to name your .nbh file DIAMIMG.nbh, move it to the phone's internal storage and flash directly (see tutorial)
Kind regards and have fun with your new roms
Click to expand...
Click to collapse
My complain is that forum is full of unimportant trash in topics and no really helpfull info. Like now, i have found a ROM, flashed it and i lost TouchFlo ) Super!
And no original ROMS, only some outdated.
Well, i am a bit tired reading this forum today within 8 hours to find more or less fresh tut, so i can not tell you exactly what is wrong, but i am telling you - i am professional software developer, not a lamer and not a pumpkin head BUT i lost in this forum, jumping from link to link.
I would delete ALL and put all in order:
Flash (ROM) files here:
Radio files here:
Boot loaders (Hard SPL or whatever it's called) here:
Flashers (Software) here:
Tutorials here:
Discussion here:
Instead i see 13248 topics with xxxxx messages inside and 1% of useful info.
Well, if you take donations then make it user friendly.
I will donate 100 USD to make it in order.
And PS - this is a problem that there are Plenty or tutorials!
Like we say in my language - brevity wit! Try to write the less and put sense the more.
Like when i read - hard SPL... then 100 lines text, cheers to authors and then - a patched bootloader..
LOL

@ROM chefs: Standardized Naming for F/W releases

Hi all you chefs out there.
As you all know the SGS is an awesome. Awesome devices have the tendency to get lots of chefs cooking even more ROMs.
In order to keep F/Ws and new releases managable it is handy to have a standard naming system for the threads in which the ROMs are released. This works best if we start sticking to one standard as early as possible because it's hard to adapt once you have 50+ ROMs threads. So here is my proposal:
[%variant% ~ %region%] [dd/mm/yy] %Name% {%version%} [%Androidbuild% ~ %baseROM%] {%launcher%} %mchangelog% [%specialfeature%]
Variables as follows:
%variant% - Not very useful right now since we can only use update.zip. Will become important once we get complete android builds (Update or Firmware)
%region% - If this is an update.zip the region of base firmware. If you focus your ROM on a specific language/country put it here.
%Name% - Name of your ROM. Whatever you want to call it.
%version% - The version of your ROM.
%Androidbuild% - This is the basebuild of android that the firmware uses. 2.1-update1 for the firmwares we have available right now. (Make it short: 2.1-u1)
%baseROM% - This is the last five symbols of the firmware you base your ROM on/that is required to install your update.zip. for example: XWJG3
%launcher% - This is the launcher you use (preferably with the version used).
%mchangelog% - Give one or two of the most important changes in this update.
%specialfeature% - One special feature of your ROM. Barebone or Online kitchen or something like that qualifies
Just some examples based on the available ROMs
[Update ~ Europe] [11/07/10] Doc's BareboneGalaxy {v.6} [2.1-u1 ~ XWJG3] {LauncherPro BETA} Optimized APKs [Barebone]
[Update ~ Arabic] [11/07/10] ??? {v1.1} [2.1-u1 ~ XWJG3] {TouchWiz3.0} ??? [FullArabic]
(Sorry for the questionmarks. I don't speak/read arabic. I wish I could :/)
[Update ~ Europe] [06/07/10] MoDaCo {r2} [2.1-u1 ~ XWJG1] {TouchWiz} JG1/SwypeFix [OnlineKitchen]
It's just a suggestion for the chefs obviously but it would be great if you guys could do this for us. Makes choosing a suitable ROM a lot easier.
PS: Anything I missed/you would like to see in the 'standard'? Don't hesitate to post

Very good idea, coming from the Nexus One dev thread - they too seemed to have adopted this method of displaying their ROMs, Themes, etc and it makes everything much easier to find and navigate. So i really do hope everyone follows this standard.

Exactly my idea. Coming for the HTC Topaz section, I know what it's like to have everybody just used their own design to get attention. It's annoying and makes searching unnecessarily difficult.
@Chefs: PLZZZ use this ;-)

I agree completely.

Gooofy said:
I agree completely.
Click to expand...
Click to collapse
yes, support! this will make life easier for everyone

Small bump ;-)

Darkstriker said:
Small bump ;-)
Click to expand...
Click to collapse
Good idea with creating a standard for thread titles.
Thus I'll use it

We really need a mod. *bump*

^^^ I second that !

Needs another bump again :S

*minibump*

One way or the other, this is going into the [READ ME] sticky, so this thread is closed.

[READ ME] Android Development section

(shamelessly copied and then modified from junkdruggler's post here)
This is a DEVELOPMENT section, not GENERAL. Do NOT post questions here!
Before continuing, read this post: http://forum.xda-developers.com/showthread.php?t=729511. It also contains a link to XDA's rules, read those as well !
Let's try to post our ROMs and threads the following way to make the forum quicker and easier to access:
Code:
[KITCHEN][WWE][08.08.08] KOKOTAS ELF(in) Hybrid Kitchen (version 1.3)
[PRJ][WWE][BETA] BRAM / NOONSKI Touch Surface 6.1 Public Beta Release Candidate Unskinned
[REF] NOONSKI Cooking Class Class of 2008/09
[UPG] HTCTOUCHP New USPLs & IPLs for Elf & Elfin
[ROM][EUR][UPD][11-07-10] Doc's BareboneGalaxy v6 [2.1-u1~XWJG3][LauncherPro BETA] Optmized APKs [Barebone]
[ROM][ARA][UPD][11-07-10] ??? v1.1 [2.1-u1~XWJG3][TouchWiz 3.0] ??? [FullArabic]
[ROM][EUR][UPD][06-07-10] MoDaCo r2 [2.1-u1~XWJG1][TouchWiz] JG1/SwypeFix [OnlineKitchen]
For ROM releases, use:
Code:
[ROM][%region%][%variant%][dd-mm-yy] %name% %version% [%Androidbuild%~%baseROM%][%launcher%] %mchangelog% [%specialfeature%]
Variables as follows:
%region% - If this is an update.zip the region of base firmware. If you focus your ROM on a specific language/country put it here. Use abbreviations: EUR (Euro), ARA (Arabic), USA (United States)
%variant% - Not very useful right now since we can only use update.zip. Will become important once we get complete android builds. Use abbreviations: UPD (Update), FW (Firmware)
%name% - Name of your ROM. Whatever you want to call it.
%version% - The version of your ROM.
%Androidbuild% - This is the basebuild of android that the firmware uses. 2.1-update1 for the firmwares we have available right now. (Make it short: 2.1-u1)
%baseROM% - This is the last five symbols of the firmware you base your ROM on/that is required to install your update.zip. for example: XWJG3
%launcher% - This is the launcher you use (preferably with the version used).
%mchangelog% - Give one or two of the most important changes in this update.
%specialfeature% - One special feature of your ROM. Barebone or Online kitchen or something like that qualifies
Just some examples based on the available ROMs
[ROM][EUR][UPD][11-07-10] Doc's BareboneGalaxy v6 [2.1-u1~XWJG3][LauncherPro BETA] Optmized APKs [Barebone]
[ROM][ARA][UPD][11-07-10] ??? v1.1 [2.1-u1~XWJG3][TouchWiz 3.0] ??? [FullArabic]
[ROM][EUR][UPD][06-07-10] MoDaCo r2 [2.1-u1~XWJG1][TouchWiz] JG1/SwypeFix [OnlineKitchen]
For upgrade tools (HSPL, SSPL, CID, SIM, etc.), use:
Code:
[UPG] Description
For complete kitchens, use:
Code:
[KITCHEN][Language] name and version (Build)
For projects, use:
Code:
[PRJ] description
For utilities, use:
Code:
[UTIL] name and version
For reference threads (tutorials, guides, etc.), use:
Code:
[REF] description
A good start to a good structure

I have tried creating a standard for the ROM naming before but for lack of a sticky, there is so far only one "chef" who uses it.
http://forum.xda-developers.com/showthread.php?t=723745

Interesting. I've just copy/pasted a different post who'se layout reminds me of other sections I've moderator, and which will look familiar to users coming from the WM forums to here. I am of course open to suggestions!
Let's discuss, critisize, and formalize. Your way of naming looks smart to me, so let me share my comments.
Your original:
[%variant% ~ %region%] [dd/mm/yy] %Name% {%version%} [%Androidbuild% ~ %baseROM%] {%launcher%} %mchangelog% [%specialfeature%]
Variables as follows:
%variant% - Not very useful right now since we can only use update.zip. Will become important once we get complete android builds (Update or Firmware)
%region% - If this is an update.zip the region of base firmware. If you focus your ROM on a specific language/country put it here.
%Name% - Name of your ROM. Whatever you want to call it.
%version% - The version of your ROM.
%Androidbuild% - This is the basebuild of android that the firmware uses. 2.1-update1 for the firmwares we have available right now. (Make it short: 2.1-u1)
%baseROM% - This is the last five symbols of the firmware you base your ROM on/that is required to install your update.zip. for example: XWJG3
%launcher% - This is the launcher you use (preferably with the version used).
%mchangelog% - Give one or two of the most important changes in this update.
%specialfeature% - One special feature of your ROM. Barebone or Online kitchen or something like that qualifies
Just some examples based on the available ROMs
[Update ~ Europe] [11/07/10] Doc's BareboneGalaxy {v.6} [2.1-u1 ~ XWJG3] {LauncherPro BETA} Optimized APKs [Barebone]
[Update ~ Arabic] [11/07/10] ??? {v1.1} [2.1-u1 ~ XWJG3] {TouchWiz3.0} ??? [FullArabic]
(Sorry for the questionmarks. I don't speak/read arabic. I wish I could :/)
[Update ~ Europe] [06/07/10] MoDaCo {r2} [2.1-u1 ~ XWJG1] {TouchWiz} JG1/SwypeFix [OnlineKitchen]
Click to expand...
Click to collapse
I would keep the [ROM] prefix, just to distinguish it from normal programs, utilities, upgrades, tutorials, etc.
I would also use abbreviations to keep things short, and cut down on whitespace. variant = [UPD/FW], region = [EUR/ARA/USA/....], AndroidBuild / baseROM, without the spacing. To prevent overkill of brackets, I would not bracket the version. Also as we are using dd/mm/yy notation, AFAIK it is more common to use - instead of /. And I really just hate curly brackets, but that's personal
Example:
[ROM][EUR][UPD][11-07-10] Doc's BareboneGalaxy v6 [2.1-u1~XWJG3][LauncherPro BETA] Optmized APKs [Barebone]
Comments ? Suggestions ?

Chainfire said:
Interesting. I've just copy/pasted a different post who'se layout reminds me of other sections I've moderator, and which will look familiar to users coming from the WM forums to here. I am of course open to suggestions!
Let's discuss, critisize, and formalize. Your way of naming looks smart to me, so let me share my comments.
Your original:
I would keep the [ROM] prefix, just to distinguish it from normal programs, utilities, upgrades, tutorials, etc.
I would also use abbreviations to keep things short, and cut down on whitespace. variant = [UPD/FW], region = [EUR/ARA/USA/....], AndroidBuild / baseROM, without the spacing. To prevent overkill of brackets, I would not bracket the version. Also as we are using dd/mm/yy notation, AFAIK it is more common to use - instead of /. And I really just hate curly brackets, but that's personal
Example:
[ROM][EUR][UPD][11-07-10] Doc's BareboneGalaxy v6 [2.1-u1~XWJG3][LauncherPro BETA] Optmized APKs [Barebone]
Comments ? Suggestions ?
Click to expand...
Click to collapse
Those sound to me like sensible modifications. Now that I think back on it the curly brackets weren't really necessary ;-) And the date... my version of Windows displays the date as dd/mm/yyyy so I'm really at a loss what is convention here. but it really doesn't matter. I like the dashes too

Alright, updated first post with the changed information.

Structure is badly needed! all people are polluting this forum with topics with only questions!

Nice kang
I think most of what I said came from a stericson post... not sure though... I like READ MEs... and stickies... and FAQs...

I see only 2 ways you are EVER gonna be able to enforce this:
1) you go modo crazy and start deleting/moving stuff massively
tho you might get tired of doing so after a week or 2 ^^
2) you find somone that can modify the vbulletin post/reply form, so that it integrates the exact syntax you'd like ppl to use to post, and deny posts if it's not correctly filled out.
GL

This does not require enforcing, nor is it an exact science.
Conventions like there are used all over XDA and are generally followed. As soon as a number of the top releasers start following it in a subforum, the rest will eventually follow. It will take a while, sure... but it will happen, once the beginners realise that a structured life is a better life.
You have the option to do things nice and structured, or you can make a mess of things, but hey it'll be the mess you have to wade around in

Well said, I like the XDA naming scheme, seems to work well. Is there a mod for this section yet? someone to sticky important posts for now would do

There's an official mod, yes, and there's me. But I'll be off on vacation in a few days, for several weeks ...

Dear Friends.
I am using GoaTrip Rom on my SGS GT i9000. Now that this rom has loads of problems, I want to install Darky's ROM.
Cud somebody help with the procedure to do the needful.
Step by Step procedure will be helpful.
Plz reply to my PM - [email protected]
Regards
M Fahim

You need to study the step-by-step of whatever ROM you choose.

Rom OP Format...DEVS READ PLEASE

Below is a format that should be used as an example of how a rom thread should look. It doesnt have to be exact. I suggest that you stay creative and use all the features in the advanced panel when creating a thread.
1. Name of rom, team, etc
2. Introduction
3. Changelog in code or php tags
4. What's included in the rom in the (apps, tweaks, scripts, addons, mods) in code of php tags
5. What works/what doesn't work in code or php tags
6. Credits (Users name-with link to (profile/github/or thread u got tweak from embedded), and what they did to help you)
7. Screenshots (2-10 different screenshots of different aspects of rom)
8. Kernel with either link to thread you got it from or github (if stock sense or cm please state that and that is enough)
9. Instructions on how to install the rom (also if special instruction for a2sd or beats audio...etc)
10. Do's and Don'ts of the rom
11. Questions & Answers section (I find this helpful to write out asked questions with solutions at the bottom of the op. I find that it cuts down on the question being asked a million times)
12. Finally the dl link
13. Additional add-ons (this can go into first post or reserved posts after)
I find the embedded link looks and feels better throughout the op if possible.
All sections should have a header with enlarged text and spaced out so people can read it easily.
I am hoping that this helps to make this section a little cleaner and easier. enjoy
The way I look at this is that it takes US weeks/days/hours to make these roms....we can take the time out to make sure that the op looks professional and clean
Also Make sure the op is fully ready before posting. I know we all get excited to release a rom but stating that half the stuff will be updated as time permits just shows that you are lazy and in a hurry which doesnt look good cause if thats the case then how does your rom run....
No posting a a rom thread without a DL link either