Hi there!
There are members here who have successfully cooked for the Vogue with each one using the kitchen that he prefers, while there are many others who have researched for hours and still have trouble setting up a kitchen.
Anyone who tried to do this without prior knowledge surely remembers how much effort is needed to learn all the steps, since the cooking process is quite complicated and there are many new things to learn. Even if one managed to setup a kitchen he might still have no idea how to port a new build to the kitchen. I have also found it difficult to learn what exactly do you need to keep from the original ROM that was shipped with the device and which of those old files can we get rid of. And the list goes on and on...
Many would love to enjoy the thrill of building their own custom ROM with the programs that they find useful, and to be able to tweak it the way they prefer.
I'm calling here on all of you who have experience cooking for the Vogue to please share your knowledge here.
If you have a kitchen setup that you would like to share, I'm sure that many members would love to make use of it!
See post #18 for a description of ROM XIP SYS OEM and LANG. Thanks to egzthunder1.
UPDATE 02/18/10
From my own personal experience and as others have mentioned in the first few posts of this thread, the easiest kitchen for a new chef is the PPCKitchen.
STEP 1: You can register at ppckitchen.org and download the latest version of the kitchen. After installing the kitchen you will need to run the updater. It will take a few seconds while it connects to the server. After that you will have an option of downloading different files. In order to cook a working ROM you will need to go to ROM Kitchens\Vogue and download the following Vogue Carrier Kitchen files, Vogue Kitchen Core, Vogue Drivers. (I don't believe you need Generic OEM Kitchen files in the above directory). Of course you will also need at least one of the Windows Mobile builds from the same directory (ROM Kitchens\Vogue).
Although the builds that show up in the updater are pretty new, yet the latest builds will not show up. In the future after having successfully cooked a ROM with one of the more stable builds from the updater, you can go get the latest builds from the PPCK website at Windows Mobile Build Discussions\Test SYS Builds. *Advanced PPCk Users only*. For now I would stick to the builds that show up in the updater.
There are also OEM files that you can download with the updater. These files have different programs that you will be able to add to your ROM. You can download PPCKitchen OEM's, PPCKitchen 240x320 OEM's, Non Freeware OEM's (don't get exited it's only a trial!), and User submitted OEM's. You don't need any of these so you can download them and check if you want the programs that's inside, if not you can delete the whole file from your kitchen folder that's in your PPCK folder.
The kitchen is very easy to use and you can now build a basic ROM.
I hope to add more to this mini tutorial within the next few days.
I agree 100%, I think it would be great if some of the experienced chefs could drop some knowledge on the rest of us, if not only so we can keep pumping out new ROMs for our Vogues.
Head over to PPCKitchen.org they have a tutorial and everything you need to cook roms, its also the easiest to use in my opinion.
As you may have noticed over the past few days, I have been trying to keep the forum a little cleaner by asking people who open new threads with questions to simply ask them in a sticked Q&A thread. This request also falls under that same premise. Please do not open new threads asking questions. Threads should only be opened to contribute to the site (roms, kitchens, skins, guides, apps, etc). Thanks.
Barogi44 said:
Head over to PPCKitchen.org they have a tutorial and everything you need to cook roms, its also the easiest to use in my opinion.
Click to expand...
Click to collapse
I also have been using the PPCkitchen and agree that it's the easiest, but I have found that it's also somewhat limiting and think it would be a good idea if those using the Ervius VK or any other kitchen would be able to help others.
egzthunder1 said:
As you may have noticed over the past few days, I have been trying to keep the forum a little cleaner by asking people who open new threads with questions to simply ask them in a sticked Q&A thread. This request also falls under that same premise. Please do not open new threads asking questions. Threads should only be opened to contribute to the site (roms, kitchens, skins, guides, apps, etc). Thanks.
Click to expand...
Click to collapse
Sorry, didn't mean to make a mess while your trying to clear things up. It must be frustrating, sort of like cleaning up the floor and having somebody walk in tracking dirt on the freshly cleaned floor!
I just thought that this would be a Tutorial type of thread where members could come and add their little bits of knowledge until we would have a lot of info gathered in one spot. Personally I still think that it's not another simple Q&A thread, although your welcome to disagree and to remove this thread if you want. I'm still hoping that this thread will become a guide for all newcomers to cooking.
When I get home tonight, I will give you a heads up on how i use PPCKitchen. I cook for personal use only and don't publish roms. In short, all I do is use is a modified version of Vin's Generic_OEM. By modified, I take out things I don't need and insert things I want. When I used to flash manila roms, this was critical as his MANILA folder has every thing needed. Now that I don't use MANILA (I replaced it it SPB Mobile Shell 3.5.3 (I LUV IT!). When a new WM build comes out, I simply pop them files in the appropriate places and run it. I am currently in love with 23529.
If your interested in what I'm doing, you can start by downloading Vin's Generic_OEM from his 28014 Thread. Just search for Generic_OEM in the thread.
Lewy1 said:
Sorry, didn't mean to make a mess while your trying to clear things up. It must be frustrating, sort of like cleaning up the floor and having somebody walk in tracking dirt on the freshly cleaned floor!
I just thought that this would be a Tutorial type of thread where members could come and add their little bits of knowledge until we would have a lot of info gathered in one spot. Personally I still think that it's not another simple Q&A thread, although your welcome to disagree and to remove this thread if you want. I'm still hoping that this thread will become a guide for all newcomers to cooking.
Click to expand...
Click to collapse
I know what your intentions were and I do not disagree with you. But there are a few things that need to be considered for making a "cooking guide" for this particular section of the site...
*There are only 3 (4 at best) active chefs for this section: Nag, Barogi, vin (if he decides to fully return), and myself. I believe that NFS will not return (personal unfounded belief).
*Most of the above chefs use PPCK. I am not saying that they don't use others like VK, but the info on cooking will be pretty much the same that you can find in the PPCK website.
*There are a slew of tutorials floating around the site (not just the Vogue section, but throughout XDA), which have a lot (and I do mean a lot) of information on how to cook.
*Cooking with other kitchens is far more involved than simply dropping build packages into PPCK. You can even get down to the nitty gritty of hex editing your rom to get more stuff out of it (ie, there is a hex change in the BA roms that allow you to have more ram available).
*Lastly, since the Vogue uses newer style roms (nbh, as opposed to older formats like nbf), learning how to cook from scratch would be kinda a waste of time (believe me, I spent the last month learning how to port a newer rom to the Blue Angel and it isn't as simple as you may think).
One of the mods (I can't remember which one right now) has a series of posts with tools, tutorials, and a bunch of other things needed to cook. What we could do is simply make a one or two post sticky with the links to the different tutorials on xda as well as on other sites (ppcgeeks has a 1100+ pages thread that talks about cooking and porting). I will see if I can get my hands on those and get them in here if that is ok with you.
egzthunder1 said:
One of the mods (I can't remember which one right now) has a series of posts with tools, tutorials, and a bunch of other things needed to cook. What we could do is simply make a one or two post sticky with the links to the different tutorials on xda as well as on other sites (ppcgeeks has a 1100+ pages thread that talks about cooking and porting). I will see if I can get my hands on those and get them in here if that is ok with you.
Click to expand...
Click to collapse
Thanks, that's perfectly fine with me. I have seen most of the stuff that you mentioned and was actually thinking along the same lines as you. If I can I will add my own little bit of knowledge like links to the various kitchens and so on. By the way there is a new kitchen, Oskitchen with new UI by airxtreme (original kitchen by Ondraster). It looks like it will be easy to use and has just been modified for the Vogue, and I'm hoping to give it a try tonight.
Lewy1 said:
Thanks, that's perfectly fine with me. I have seen most of the stuff that you mentioned and was actually thinking along the same lines as you. If I can I will add my own little bit of knowledge like links to the various kitchens and so on. By the way there is a new kitchen, Oskitchen with new GUI by airxtreme (original kitchen by Ondraster). It looks like it will be easy to use and has just been modified for the Vogue, and I'm hoping to give it a try tonight.
Click to expand...
Click to collapse
Yes, I did see that one. I had tried oskitchen before and it isn't too bad (still preferred Ervius though). However, this new UI seems a little more user friendly...
Start out with PPCK. It works well, most users will not notice the limitations.
Biggest thing with making your own ROM's is getting all of the Reg edits that need to be included.
Good Luck! PS Start with build 23529 it seems to be really stable and fast!
First post updated with mini tutorial.
Lmiller1708 said:
Biggest thing with making your own ROM's is getting all of the Reg edits that need to be included.
Click to expand...
Click to collapse
Perhaps we can use this thread to gather up those types of regedits in one place. It would also be good to have guides for new cooks on how to add things like EzInput 2.1 (with working vibration) and Long Press End Key, BT Pan and Alarm functionality (while plugged in). Most of the newer roms have old or incomplete implementations of these features. vin was the last person to get many of these features all together in one place. With the age of the Vogue many of the cooks are trading up to newer devices and much of that knowledge is getting lost.
codf4ther said:
Perhaps we can use this thread to gather up those types of regedits in one place. It would also be good to have guides for new cooks on how to add things like EzInput 2.1 (with working vibration) and Long Press End Key, BT Pan and Alarm functionality (while plugged in). Most of the newer roms have old or incomplete implementations of these features. vin was the last person to get many of these features all together in one place. With the age of the Vogue many of the cooks are trading up to newer devices and much of that knowledge is getting lost.
Click to expand...
Click to collapse
Are you talking bout me ?
egzthunder1 said:
Are you talking bout me ?
Click to expand...
Click to collapse
No sir, not trying to single anyone out. I've tried pretty much every rom released here and on PPCGeeks I haven't tried your latest ones labeled MetroPCS. I'll flash you latest tonight and try it out for a few days.
just uploaded 28230. Try that one and let me know if you like it...
btw, I was joking... don't sweat it. I don't get so easily offended
tharris297 said:
When I get home tonight, I will give you a heads up on how i use PPCKitchen. I cook for personal use only and don't publish roms. In short, all I do is use is a modified version of Vin's Generic_OEM. By modified, I take out things I don't need and insert things I want. When I used to flash manila roms, this was critical as his MANILA folder has every thing needed. Now that I don't use MANILA (I replaced it it SPB Mobile Shell 3.5.3 (I LUV IT!). When a new WM build comes out, I simply pop them files in the appropriate places and run it. I am currently in love with 23529.
If your interested in what I'm doing, you can start by downloading Vin's Generic_OEM from his 28014 Thread. Just search for Generic_OEM in the thread.
Click to expand...
Click to collapse
I don't know if you sent this over via PM but I'd be interested in reading it too. I tried replacing the Generic_OEM.rar in the kitchen folder with the one from vin, but the kitchen won't startup after i do that.
codf4ther said:
I don't know if you sent this over via PM but I'd be interested in reading it too. I tried replacing the Generic_OEM.rar in the kitchen folder with the one from vin, but the kitchen won't startup after i do that.
Click to expand...
Click to collapse
The reason is that Vin's packages are not "kitchen ready". What he posted is in essence a dump of the Mega rom. The packages have to be worked on in a one by one basis to get them to work with PPCK. There is a nice guide on how to do that in the forum at PPCKitchen.org.
Hey Lewy1,
You are off to a good start. I have been giving your idea some thought and if you truly want this to be a "learning resource" for new chefs, you may want to start by describing a few basic concepts as well.
[highlight]ROM[/highlight]
In essence the Operating System with all the necessary files and programs that make up for what you have on your device. This contains things that are general to all devices as well as certain files and folders that are specific to each particular device (hence, the reason why you cannot flash a rom from a Blue Angel into a Vogue and vice-versa). Once a rom is obtained by dumping it, the dump will have a bunch of folders and files, which need to be turned into something "cookable". There exist several applications that can (and must be used) in order to accomplish this.
After all the things in the "dump" are sorted out and manipulated, the rom will essentially turn into 4 main parts: XIP, SYS, OEM, and Lang packages.
[highlight]XIP[/highlight]
The XIP is what holds the core of the OS. This is what holds the Native Kernel of the particular device as well. In order to port a rom to a device, one cannot simply replace the XIP with a new one. The XIP of the new OS must be "implanted" into the XIP of the base rom of the device. The reason for this is that there are many files that can simply be replaced in the XIP, but some must remain untouched as they hold key elements for the proper functioning of the device (Native Kernel).
[highlight]SYS[/highlight]
The SYS folder will have packages with software that the device may or may not need to run properly. This holds things such as the Shell (your UI), Office, core applications, etc. A lot of these packages can be removed from the SYS in order to make space for other apps that the chef maybe interested in having. However, great care must be taken when removing/adding packages since some packages are needed for the device to even be able to boot. Likewise, having too many packages will render the rom un-flashable since most devices have a specific size of rom that they cannot go over. In the case of latter devices, the available space for rom has gone up dramatically. For instance, the Vogue has roughly 90 MB of space for the rom. This is more than plenty to cook a lot of apps without too many issues. There are older devices such as the Blue Angel, where the size of the rom is limited to 32 MB, which forces most cooks to remove packages and compress things as much as possible to even have a bootable rom (keep in mind that most of the time, builds are coming with more and more space requirements).
On top of all this, there are the resolution requirements. Most packages will come with a second folder of a similar name with the resolution added. For example, Base will have another folder called Base_96DPI. The chef will have to be careful on what he/she puts to be cooked as having different resolution packages can make the device either not boot, or look weird (out of scale images) if it does boot
[highlight]OEM[/highlight]
The OEM normally holds fixes and programs that the cook could not fit in the SYS. It also hold drivers, sometimes even Language packs among other things.
[highlight]Lang[/highlight]
These are language and location specific modules. The chefs use the location modules to make roms for different languages and locations. It is usually a four character code that determines which country/language the rom is made for. For instance, 0409 is WWE.
There are many other basic concepts (such as Virtual Memory allocation) that could be discussed, but for now, these basic definitions should help the average person understand what they are dealing with when they see a new set of packages coming out on PPCK,
Hope this helps the cause
egzthunder1 said:
Hey Lewy1,
You are off to a good start. I have been giving your idea some thought and if you truly want this to be a "learning resource" for new chefs, you may want to start by describing a few basic concepts as well.
Click to expand...
Click to collapse
Thanks! Great Info I'll add it to the first post.
Related
Please will someone post ONE rom without removing .rgu files before posting.
I just want to cook my own ROM.
...
Cmon, guys
I was about to create the exact same thread.
Until a few month ago, I used to re-cook the roms I downloaded here to get rid of the unusefull applications and add my customisation.
Now that wm6.1 is out, I wanted to switch to it but I was unable to find a rom with this f*** dsm and rgu that are mandatory for a clean cooking.
Cookers, why the hell are you removing this files ?!?
Is it to save a few kb which is stupid regarding the pain in the ass trying to improve the rom after this suppression ? (Or did I miss a major revolution in the cooking process that make them unusefull to create packages and registry hives ?)
So could anybody give an advice for a good ROM (light and fast) where this RGU and DSM remains ?
Exactly,
recently I switched from Prophet from Trinity.
I couldn't wait to compare its performances to previous device, but was unpleasantly surprised to see that almost NONE of the ROMs posted in Trinity section is editable.
On the contrary Prophet ROM section is way more advanced.
In the end, I thought that ROMs are (at least ones posted here) kind of public property, and that the they shouldn't be locked (by removing rgu files prior to posting, or putting the time code on them!!!). If you want to sell them - then go apply for job at Micr0s0ft.
On the other hand - I can understand that someone is affraid that someone will overtake his/her work and claim it as their own. But again, we are here to help to each, and I never personally published any of my own modified ROMs - due to respect to the author. It would be good practice that someone who makes modification - always mentiones which ROM is used as a base for development.
Just imagine what would happen if Bepe, Mamaich, Olipro and other real developers made their tools just for themselves!
Cheers!
There's something I can't understand...
Why do you need to edit released ROMs, when you have access to ROM kitchens?
My best guess is that you don't want to spend endless hours figuring out the best tweaks, solving problems, creating packages, and so on, when you can have it all done by others.
Remember one thing:
None of the cookers here are releasing ROMs for profit. We do it as courtesy, to help the less skilled, so they can also have a more updated and efficient system running on their devices.
Cookers aren't by any means obliged to reveal their little secrets, which for you may seem trivial, but in fact, it may be the sum of many hours testing.
Cooking with a untouched kitchen is a good way to get to know how things work, and to improve your own cooking skills. So it's not respectful of you to say that cookers have to release their ROMs editable, or any other related demand for that matter, whether you release your edits or not.
It's the cookers choice to release a ROM as he see fit, and it's the user choice to use it or not.
I don't have a problem with the so called "competition", since I'm not here to compete. I'm not here to win, rather to provide an alternative. But it's hard for me to give up my work just like that.
I wouldn't have any problem providing a kitchen, but unfortunately my main source is XDA-Developers, so I also rely on others to get a base for my work. My skill level is not yet that high, but I'm always trying to improve myself.
I'm sorry if I'm offending someone, but I needed to speak my mind...
FInixNOver said:
There's something I can't understand...
Why do you need to edit released ROMs, when you have access to ROM kitchens?
My best guess is that you don't want to spend endless hours figuring out the best tweaks, solving problems, creating packages, and so on, when you can have it all done by others.
Remember one thing:
None of the cookers here are releasing ROMs for profit. We do it as courtesy, to help the less skilled, so they can also have a more updated and efficient system running on their devices.
Cookers aren't by any means obliged to reveal their little secrets, which for you may seem trivial, but in fact, it may be the sum of many hours testing.
Cooking with a untouched kitchen is a good way to get to know how things work, and to improve your own cooking skills. So it's not respectful of you to say that cookers have to release their ROMs editable, or any other related demand for that matter, whether you release your edits or not.
It's the cookers choice to release a ROM as he see fit, and it's the user choice to use it or not.
I don't have a problem with the so called "competition", since I'm not here to compete. I'm not here to win, rather to provide an alternative. But it's hard for me to give up my work just like that.
I wouldn't have any problem providing a kitchen, but unfortunately my main source is XDA-Developers, so I also rely on others to get a base for my work. My skill level is not yet that high, but I'm always trying to improve myself.
I'm sorry if I'm offending someone, but I needed to speak my mind...
Click to expand...
Click to collapse
+1 you've said everything
Hi, FInixNOver,
well I am glad you replied. Although better anything than nothing.
Watch now:
"Why do you need to edit released ROMs, when you have access to ROM kitchens?"
Well, why do you need kitchens (and tools) - why don't you develop them by yourself?
You say
"So it's not respectful of you to say that cookers have to release their ROMs editable, or any other related demand for that matter, whether you release your edits or not".
No one said they have to. But after hours of testing and achieving something which only you succeeded to - to keep it as a secret? And not share it with the "less skilled" on the forum? I understand if someone invested hours in artistic-visual development of the ROM - everyone will recognize that as effort - but removing .rgu files used for creating the registry during ROM building - is creative???
Or when I dump the ROM and see the folder named "Don't touch my ROM"?
Cmon, thats pure blsht!!!
What if someone makes "Don't touch my Hard-SPL"?
phnikola said:
Hi, FInixNOver,
well I am glad you replied. Although better anything than nothing.
Watch now:
"Why do you need to edit released ROMs, when you have access to ROM kitchens?"
Well, why do you need kitchens (and tools) - why don't you develop them by yourself?
You say
"So it's not respectful of you to say that cookers have to release their ROMs editable, or any other related demand for that matter, whether you release your edits or not".
No one said they have to. But after hours of testing and achieving something which only you succeeded to - to keep it as a secret? And not share it with the "less skilled" on the forum? I understand if someone invested hours in artistic-visual development of the ROM - everyone will recognize that as effort - but removing .rgu files used for creating the registry during ROM building - is creative???
Or when I dump the ROM and see the folder named "Don't touch my ROM"?
Cmon, thats pure blsht!!!
What if someone makes "Don't touch my Hard-SPL"?
Click to expand...
Click to collapse
You may be right about the tools, without them it would have been very hard to get many of the tasks completed successfully and probably I wouldn't have even started cooking.
But, how on earth would you be able to build a ROM without a kitchen?!! You certainly cannot make an omelet without the eggs, now can you?
And I never demanded any tools from anyone or even kitchen. When I have a request or something to say, I usually politely ask or give a suggestion.
You should try to create you own ROM before making assumptions about what cookers should keep a secret or not. Then you'll notice that cookers help each other whenever possible (e.g. when something important is fixed).
And I do share my findings, mainly in my ROMs obviously!! That doesn't mean I have to expose all my work. It's necessary to research a bit. You'll find it rewarding.
Also, almost all of the art work in my ROMs is my hard work, and it's painful to see it scattered around without so much as a credit (I'm not asking to be paid or anything). So, why not protect my work?
Tweaks? That's a whole different subject, the ones you may find helpful other may not, it's up to each one to use the one that will best suit your needs.
You will also learn, that most times, a cooker will not mess with the RGUs in a kitchen. Instead, a brand new package is created just for registry tweaks, this way the changes are easily tracked down. This being said, I can easily build a ROM, that you'll be able to dump and repackage, but you won't find my registry tweaks. Would that work for you? Because, I find this process to be more deceiving than providing the ROM without RGUs and DSMs.
You're making it sound like I say less skilled persons in a bad way. Every user is a potential cooker. Everything is available. Sometimes, you just have to dig a little deeper.
Some find it to hard to learn, others get what they need from the available options, others, well... they're just too damn lazy. But hey, everyone's got their reason, and who the hell am I to judge them?!!
"Don't touch my hard SPL"
This is a funny one!!! You have quite a mess in you attic. You're mixing 2 very different subjects...
I know one thing!! I wasn't fully satisfied, with the options I had, so I decided to get my hands dirty and do it myself. I learn everyday, and I have yet plenty to learn.
My conscience rests easy, as I've made some contributions, maybe not very important ones, but never the less...
I released some fine ROM(not perfect, I'm well aware of that) if I may say so, and made some users happy.
I don't want to start a war or anything. This all subject of protecting or not the cooker's work has already been extensively discussed, and I gave my opinion about it.
In the end I can say:
I've paid my dues. Have you?
OK, I wont argue anymore but will not change my oppinion either.
I am closing this thread by posting HTC Trinity - Complete Cooking tutorial for begginers in the forum.
Maybe my debts will be payed now!
Now let us be more useful and post comments and EDITABLE ROMs!
In the end - I would do that for you as a forum member
Cheers!
FInixNOver said:
There's something I can't understand...
Why do you need to edit released ROMs, when you have access to ROM kitchens?
Click to expand...
Click to collapse
To my mind, kitchen are not made to cook a rom but to learn to the newbies how it works. It's far from beeing a good solution to realy cleanly cook roms (often buggy, not possible to have an up to date OS, ...). However it's really instructive and it's great work from the creators of theese kitchens.
FInixNOver said:
My best guess is that you don't want to spend endless hours figuring out the best tweaks, solving problems, creating packages, and so on, when you can have it all done by others.
Click to expand...
Click to collapse
It's right but it's exactly the point of development, saving hours by using existing libraries to be able to create something realy new that's not another copy of something existing.
Do you know the meaning of a Community of Practice or did you forgot the first function of this board ?
Moreover, you must know that it's way more painfull to cook a rom without kitchen than with a kitchen, even if the result is best.
Finally, this kind of "protection" is quite useless as the rom is still dumpable and editable, it's just a bit more painfull as you need to find the missing files from other roms or from packages.
I was curently working on a rom editor to enable cookers to save time cooking rom with a GUI but I think I will stop the project for a time to try to develop a tool that will be able to recreate the missing dsm, rgu and packages.sof to proove:
1) I'm not a lazy lamer
2) Sharing knowledge is much more profitable for the community than keeping it for itself (even if it has already been done a hundred of times by bepe and so many other on this board)
However, don't think I don't respect cookers work but I think this point stands against this board main function, this will be my way to pay my dues
@phnikola : I found this rom http://forum.xda-developers.com/showthread.php?t=391450&highlight=KAEW working quite well (light, fast, stable and recent build) where the rgu, dsm and .sof are still existing. If you want to use another ROM, just copy all the rgu, dsm and packages.sof from this one to the dump directory of the other rom
Peace
@ phnikola
I welcome your gesture and I'll be more than happy to make some contribution, to make it the best tutorial that I never had.
@ tonio94
Well, my understanding of kitchen is the set that includes the ROM files, packages, tools (whether they are batch files, or fancy tools) used to edit and build the ROM. As I say that's only my understanding of it. I may as well be wrong. And I'm very thankful for the effort and hard work put into developing all the tools that can make our cooking experience so much better
I think you're missing my point. I'm all in favour of sharing. And I try to do it as much as I can, but you may also be aware that even though programmers may use the same libraries, they often protect their final work, so that other cannot take credit for it.
The same happens with ROMs. Altough I'm using the same base as many others to create my ROMs, the final result is different from cooker to cooker, and I can only speak for myself when I say that the main reason for protecting my work is to avoid having my work ripped off.
I have absolutely nothing against making available the kitchen as bug free as possible, so that everyone can make their own customization of it.
I'm well aware that this protection can only slowdown the process of editing the ROM, but it's a way to make it a bit harder for others (I mean only the ones whose sole purpose is to take someone elses's work as their own), to take my work.
Sometimes, just because of a handfull of gready people that take other people work and make it their own without any credits, the rest of the community ends up paying for it.
I wish I had some developer/programmer skils, so i could make a bigger contribution to this community, but unfortunately I've never learned that (however I'm hoping to work on it someday).
In the whole spirit of sharing, I'm going to release some treats, just to prove that it's was never my intention to undermine the work of new cookers (what am i saying?!! I'm also a new cooker!! and a noob for that matter ), I just wanted to protect myself.
FInixNOver said:
In the whole spirit of sharing, I'm going to release some treats, just to prove that it's was never my intention to undermine the work of new cookers (what am i saying?!! I'm also a new cooker!! and a noob for that matter ), I just wanted to protect myself.
Click to expand...
Click to collapse
I have a respect to that, mate
I think your ROMs are among the best. Keep up the good work
Cheers!
tonio94 said:
@phnikola : I found this rom http://forum.xda-developers.com/showthread.php?t=391450&highlight=KAEW working quite well (light, fast, stable and recent build) where the rgu, dsm and .sof are still existing. If you want to use another ROM, just copy all the rgu, dsm and packages.sof from this one to the dump directory of the other rom
Click to expand...
Click to collapse
Thanks a lot, tonio94!
Will try it as soon as download completes
FInixNOver said:
@ phnikola
In the whole spirit of sharing, I'm going to release some treats, just to prove that it's was never my intention to undermine the work of new cookers (what am i saying?!! I'm also a new cooker!! and a noob for that matter ), I just wanted to protect myself.
Click to expand...
Click to collapse
Hi FInixNOver
I don't normally get involved in these threads, but once again I have to admire the way you avoid an argument with yet another member of the community who seems to just take, take, take.
Had he and others bothered to have a look at not just the quantity and quality of ROMs you produce for everyone but the feedback and replies you give on a daily basis to people with problems, maybe he would have a clearer idea as to who the givers are in this forum.
You guys give up your time and effort for free so that others (including myself) can benefit and enjoy the fruits of your work. To show any anger or frustration is ridiculous. At least 70% of the people in Trinity forums have tried and enjoyed your ROMs. And yet still they expect you to give more. Incredible...
Mattster.
Mattster_spv said:
Hi FInixNOver
I don't normally get involved in these threads, but once again I have to admire the way you avoid an argument with yet another member of the community who seems to just take, take, take.
Had he and others bothered to have a look at not just the quantity and quality of ROMs you produce for everyone but the feedback and replies you give on a daily basis to people with problems, maybe he would have a clearer idea as to who the givers are in this forum.
You guys give up your time and effort for free so that others (including myself) can benefit and enjoy the fruits of your work. To show any anger or frustration is ridiculous. At least 70% of the people in Trinity forums have tried and enjoyed your ROMs. And yet still they expect you to give more. Incredible...
Mattster.
Click to expand...
Click to collapse
Man, I already posted that his ROMs are excellent, but you have a real problem with your selfesteem. Anyway we came to agreement - so be more useful and post in another thread
It would be great building a rom based on the Benchmarks of the roms wich you can find here http://forum.xda-developers.com/showthread.php?t=406640
The Chefs need to work together and exchange what they did in specific to get good scores in the sectors they lead and have best results.
I would exchange my knowledge. Please join this Project and lets make a fantastic rom.
What do you think about this ?
I think about a meeting on a chat with only developrs and we exchange our thoughts and knowledge.
Do you think it'd be that simple for everyone to agree upon which tweaks to enable, which ones leave out, as well as applications?
Some of them are standard procedure, but the rest depends on each different chef.
The first question would be: a light ROM, or a full-feature packed, at the cost of performance?
For my part, I usually cripple most of my ROMs to the mininum, adding afterwards only the apps I need.
Registry tweaking also is quite aggressive.
I don't like all the bloat in most of the ROMs, but that's what most users are looking for.
As for eye candy, I never integrate it at the cost of performance.
So the question would be: what do CHEFS want VS what do USERS want.
If you want to take this to the next level, you'll have to set a date for the meeting.
I'd recommend IRC, since not many ppl use jabber. MSN sucks, so...
adwinp said:
Do you think it'd be that simple for everyone to agree upon which tweaks to enable, which ones leave out, as well as applications?
Some of them are standard procedure, but the rest depends on each different chef.
The first question would be: a light ROM, or a full-feature packed, at the cost of performance?
For my part, I usually cripple most of my ROMs to the mininum, adding afterwards only the apps I need.
Registry tweaking also is quite aggressive.
I don't like all the bloat in most of the ROMs, but that's what most users are looking for.
As for eye candy, I never integrate it at the cost of performance.
So the question would be: what do CHEFS want VS what do USERS want.
If you want to take this to the next level, you'll have to set a date for the meeting.
I'd recommend IRC, since not many ppl use jabber. MSN sucks, so...
Click to expand...
Click to collapse
Well, I do think research will lead to a certain extra insight.
For example: I tested the recent Swtos ROMs: they are (real) fast, all three of them.
Why? Is it because he left something out, did he combine things, did he add something? (please tell us Swtos...)
The problem with this kind of collaboration is that cooks have to share their work. And their time...
Well, most experienced chefs have pretty established routines for performance gains.
Here's a quick MUST DO checklist for a good ROM:
1: remove bloat
2: tweak registry (services, caches, etc...)
3: DSM grouping
4: G'Reloc
5: Pagepool
Anybody with a little advanced knowledge of the windows internals can handle the first 2 tasks.
adwinp said:
Well, most experienced chefs have pretty established routines for performance gains.
Here's a quick MUST DO checklist for a good ROM:
1: remove bloat
2: tweak registry (services, caches, etc...)
3: DSM grouping
4: G'Reloc
5: Pagepool
Anybody with a little advanced knowledge of the windows internals can handle the first 2 tasks.
Click to expand...
Click to collapse
Doesn't that "lock" your ROM and come in contradiction with most thoughts exposed in the locked ROM thread?
tnyynt said:
Doesn't that "lock" your ROM and come in contradiction with most thoughts exposed in the locked ROM thread?
Click to expand...
Click to collapse
Yes it does, then again, it's not a compulsory step.
Every chef has his own preferences.
tnyynt said:
Doesn't that "lock" your ROM and come in contradiction with most thoughts exposed in the locked ROM thread?
Click to expand...
Click to collapse
May better to publish "Tree" of project (OEM,SYS,etc)?
Nothing new - look to opensource
But who will moderate it?
It is the big work, I think.
There are many tutorials, documents and even video presentations on the forum. Kitchens may differ according to device but the basic principles are the same. Search for them and do lots of research!
tnyynt said:
There are many tutorials, documents and even video presentations on the forum. Kitchens may differ according to device but the basic principles are the same. Search for them and do lots of research!
Click to expand...
Click to collapse
I guess they are not asking about how to cook a ROM... but they try to invite people (especially ROM chefs) to collaborate... and sharing how is the best way to cook a good ROM...
People that only want to use Android, and have NO clue about Linux or programming PLEASE REFRAIN FROM POSTING HERE
First off credits goto all those working hard and having sleepless nights, people like: dcordes, netripper, druidu and all those I didnt mention!
I have just made this thread to get developers a kickstart, so that they dont have to read hundreds and hundreds of posts.
==========
IRC: #htc-linux @ Freenode
==========
READ: http://linuxtogo.org/~lgorris/kaiser-bootkit/README.txt
Getting the kernel (taken from http://forum.xda-developers.com/showthread.php?p=2269384#post2269384 ... credits to dwaradzyn): (UPDATED, new ARM toolchain and now working)
Code:
mkdir ~/android
cd ~/android
git clone git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git
cd kernel
git checkout -b htc-msm-2.6.25 origin/htc-msm-2.6.25
cd ..
wget http://www.codesourcery.com/gnu_toolchains/arm/portal/package3382/public/arm-none-eabi/arm-2008q3-39-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
tar xvjf arm-2008q3-39-arm-none-eabi-i686-pc-linux-gnu.tar.bz2\?lite\=arm
cd kernel
make htcraphael_defconfig ARCH=arm
export PATH=~/android/arm-2008q3/bin:$PATH
make zImage ARCH=arm CROSS_COMPILE=arm-none-eabi-
Now the file ~/android-kernel/kernel/arch/arm/boot/zImage is ready to be put on your phone and you can boot it with haret's newest version (1.5.2 works fine) ... downloadable from: http://www.handhelds.org/~koconnor/haret/
Open your favourite text editor to create the file "DEFAULT.txt" and put the following in it:
Code:
set MTYPE 1910
set KERNEL zImage
set INITRD android.bin
set RAMSIZE 0x5e
set RAMADDR 0x10000000
set cmdline "root=/dev/ram0 rp init=/init console=tty0 mem=94M"
bootlinux
Get the file android.bin from http://linuxtogo.org/~lgorris/kaiser-bootkit/ and put it in the same directory as haret.exe, default.txt and zImage.
Is the android.bin in http://h3po.de/public/diamond_android_0.8.zip the same? (Havent checked)
=====
Now the new points of attention are:
1. Touchscreen calibration:
I have seen people talking about a red dot in the upper left corner, I have seen it once so far and didnt notice any major miss calibration when using the dev tools > pointer locator ... the only this malfunctioning is the x inversion and that you need to double tab (or is this standard behaviour? It looks like it remembers the last pressed location). Also the onscreen keyboard is very flickery, minor issue should be easy to fix (during loading it looks like it is flickering on the readout of the touchscreen).
2. Hardware support:
Adding various support for hardware, to output sound and all other "required to call" fuctionality.
Also not forgetting to access internal memory, maybe the best workaround to loading a fully fledged Android is to make a minimal initrd to setup internal storage and from there load the rest. Should be much easier when it all gets incorporated into a ROM, instead of loading with haret ... which poses serious problems regarding initrd loading and who wants WM6x/7 on his phone anyway when Android becomes usable. Loading from haret does make working with it for now a little easier. Maybe a GRUB like approach and loading straight from a filesystem (ROM or internal storage)?
==========
Some other request:
Pointers to Android OS sources or atleast a working 1.0 (latest branch?) initrd.
==========
General tips:
Going back to desktop: insert and remove stylus.
Selecting and opening, use double tabbing and mirror x for now.
Using onscreen keyboard: havent figured it out yet sadly.
=========
Ill try to update the post, also PLEASE people refrain yourself from posting in this thread ... let's make a good go at keeping it clean. If you do not intend to be working on getting Linux / Android to work on the Diamond and family please post somewhere else. No harsh feelings, but threads getting cluttered with "Great work!" and "wehn iz android really workn on me phone?" do mess things up by quite a bit.
DO NOT ASK FOR REQUESTS, focus is on the basics first ... input, output and storage.
==========
Dont forget to check: http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux
==========
Developers, please post updated links / patches and all that would help us make progression.
//placeholder for useful links
Original thread (very bloated with comments and hard to dig through, dont let it happen here): http://forum.xda-developers.com/showthread.php?t=402002
Complete working Android 0.8, "extract and run" ala Plug 'n Pray: http://h3po.de/public/diamond_android_0.8.zip
Wikipage: http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux
Haret: http://www.handhelds.org/~koconnor/haret/
Howto for kernel building: http://forum.xda-developers.com/showthread.php?p=2269384#post2269384 (replace htc-msm with htc-msm-2.6.25)
// placeholder for points that need attention
1. Touchscreen input, calibration and sensitivity.
2. Latest sources to build our own initrd for Android OS.
3. Storage accessibility.
question???
why not put this in the thread that is already running on this ????
why on earth does it need a new thread?
only a question : if I try this Android on my Diamond , the WM6.1 will be delete ? or I can have it also?
P.S.
sorry for my bad english
yuco91 said:
only a question : if I try this Android on my Diamond , the WM6.1 will be delete ? or I can have it also?
P.S.
sorry for my bad english
Click to expand...
Click to collapse
beware.....you can brick your phone if you don't know what you are doing!
liamhere said:
beware.....you can brick your phone if you don't know what you are doing!
Click to expand...
Click to collapse
ok, but you not have aswered at my questions .....
this sounds quite interesting...
Android, is a serious alternative now to Windows o/s, yes?
What are the selling points compared to windows???
Why are there not clear and concise instructions on how to install android???
Does android offer the use of the line 2 facility like 6.1?
I notice the huge Hype with the launch of the G1 phone, can someone offer some screen shots of what it looks like on the diamond please???
cheers
What???? Look I love Mobile phones, Ive bought every high end phone scince the Nokia 8800, but this is way beyond my pay grade, can you ell me how to do this? Im a junkie for utilities and Roms, and etc, but this is really past my skill level. Ive searched and read the thread but I can't get past the first stage. Please help me out, I really want to learn.
liamhere said:
why not put this in the thread that is already running on this ????
why on earth does it need a new thread?
Click to expand...
Click to collapse
cause 581 pages is hard to follow... and OP has sumarized it well...
zmob123 said:
What???? Look I love Mobile phones, Ive bought every high end phone scince the Nokia 8800, but this is way beyond my pay grade, can you ell me how to do this? Im a junkie for utilities and Roms, and etc, but this is really past my skill level. Ive searched and read the thread but I can't get past the first stage. Please help me out, I really want to learn.
Click to expand...
Click to collapse
dont bother usable android version isnt ready for general use (yet)...
not ready?
so how ready currently is it???
and do we have the choice of looking at screen shots???
does it support multi lines?
Was wm6.1 ready? - questionable!
crystal_clear said:
Android, is a serious alternative now to Windows o/s, yes?
What are the selling points compared to windows???
Why are there not clear and concise instructions on how to install android???
Does android offer the use of the line 2 facility like 6.1?
I notice the huge Hype with the launch of the G1 phone, can someone offer some screen shots of what it looks like on the diamond please???
cheers
Click to expand...
Click to collapse
no real screen shots...as it not really running RIGHT on diamond yet...
don't put this on and think your have a new all singing and dancing phone
YOU WON'T....NOT YET ANY HOW
has anyone.....
ok, your point that its not running at moment taken on board...
Has anyone had the idea yet to startup a directory for interested parties to be contacted to take part in trials - once its in the stage of being ready???
I would like to be considered, as i absolutely fully abuse all the facilities i have available to my via orange uk.
And do actively find the wm6.1 platform fails me seriously at times due to usage.
Development is open, just follow the important topic.
All I see is that this topic confuses people.
Bad idea starting this.
Riel said:
Development is open, just follow the important topic.
All I see is that this topic confuses people.
Bad idea starting this.
Click to expand...
Click to collapse
we agree to agree....your my new friend now
Delete this topic.
My cats breath smells like cat food.....
I see that this topic is confusing people already, this is mainly due to the fact 90% of the repliers DID NOT READ MY POST!
As I have stated before:
The basics still need to be worked on; input, output and storage.
People that only want to use Android should refrain from posting in this thread! I made this thread so digging in the old thread can be kept to a minimum, what gets added there I will try to add here too.
I just wanted to encourage people that know what they are doing with a headstart, I myself have been working with Linux since 1998 and reading the "delete this thread" posts really does not support encourage me to help you guys.
As for an example, some random programmer with a Diamond googles for Android and finds hey this might work on my phone (like happened to me) ... the next he will go trough hours of reading useless and outdated posts, not really helping you further.
Then you decide to read from the end back forward, even more useless posts are read and finaly you get a minimum set of files that works ... what now? No sources, no nothing to be found after reading beginning and end of the posts, so you decide to read the WHOLE thread and still NO progression after a full day of endless reading.
So my simple request was to summarize EVERYTHING developers can use to get started and NOT spend one day now or two/three days in the future looking at outdated posts and reinventing the wheel.
I for example did reinvent the wheel and started from the start of the thread, where I spend downloading the git sources from Andriod and started compiling ... same problem, started on output first ... framebuffer ... then I conclude lets start from the end and notice people already gotten something running ... NOT really helpful if you ask me.
So any mod, please delete all the useless posts in this thread. I have no problem with continueing in the old thread, but it will not progress us any further if its not cleaned up.
So people that only want to use Android, and have NO clue about Linux or programming PLEASE REFRAIN FROM POSTING HERE
So here is my summary of posts to be deleted:
4: Original thread is too long, doesnt help new developers start off where they should start.
5: Dont post in this thread, it will not delete WM6x.
6: Answer to post 6, dont post here unless you know what your doing.
7: Please dont formulate such questions here!
8: It does not work correctly, seams you just want to use Android and have no clue what your working with. Please do not post such questions here.
9: Please no learing here, learing can be done on other platforms.
11: It barely works, raw input and working output, some other major and minor functionallity is there but does not work correctly yet. Please dont ask these questions.
13: Trial and testing will be done trough progress, we dont need people that just want to use Android in this thread.
14: Sorry that it seems to confuse people, it is mainly due to people not knowing what this is all about and asking questions that should not be asked in the first place. Let alone they EVEN read every word here!
15: Good luck reinventing the wheel.
16: A webdesigner asking to close this topic ... not really helpful and discouraging.
17: Please remove yourself from this forum!
Thanks in advance.
ouch
...how to make and break friends in one single post
sorry this thread is only for the "special people"
us plebs must not comment in the thread...we have been told
THE END!
Hi!
You may know me as the guy who made blownfuze.org. I've done it again (I'm doing it, rather) and the address is tilt2.blownfuze.org. Basically it's a good place to unleash your phone, beginners to vets, while hiding from ad banners, thread chaos and rapidshare links.
The site, targeted specifically at the AT&T crowd but useful for all TP2 owners, is divided into a dozen chapters including how to flash a rom and my reflections on the various existing roms, the usual stuff to install (like flash, mortscript, MSCF and MSVC), a collection of Opera builds and other browsers and RSS readers, tweaking tools (advanced config, hd tweak), email guidance, GPS stuff, multimedia (players, tones), recreational stuff (dopewars, facebook), expert stuff (vpn client, packet sniffing) and perhaps most importantly what you need to get your phone back to its out-of-the-box stock condition (the software at least) for warranty compliance if you have ever flashed anything. It's the kind of site you might bookmark.
I only recently started this thing and though it is a little premature to post it publicly like this (it will get better over time..) the important sections like installing hardspl, flashing roms and warranty issues, they're good to go and I got some fresh cabs lined up for you too so c'mon down to tilt2.blownfuze.org.
In addition to plugging my site (thanks xda mods), the purpose of this thread is to invite suggestions from you (for example this part is good or that sucks or you should add this and remove that or cite this developer for that cab) so please do that, I will listen, or you can contact me in the contact form thingy at the bottom of my site.
Yours, Doug
Thanks Doug. Your sites are AWESOME and very useful! I don't have a fuze but I've found some sweet programs on your site for my tilt. I look forward to the new site.
Looking good, thank you!
great site, great infos. many thanks.
Looks very good actually, bookmarked it and having a good flick through now. Some very very usefull stuff on there!
Id be tempted to suggest trying to improve the GUI a bit though, theres an awfull lotta text sitting there.
Im Feelin it
This is perfect, Everything works and enhances the phone. Cant complain
thx for the repo guide
NB: Your ZoomAdds thread (http://forum.xda-developers.com/showthread.php?t=572270 -- linked to in section 5) has been superseded by this one: http://forum.xda-developers.com/showthread.php?t=578420 -- the earleir one is a version that can't be uninstalled.
I've been reading the forums for two days now and have gleaned lots of useful information in the dumping/building of WP7 (emulator) ROMs. I haven't, however, come across any information on replacing modules in the WP7 context.
While reversmode generates correct-looking output, it renders the built ROM unbootable; I'm guessing it's not built correctly.
To backtrack what I did...
I used the newer dumprom.pl, which spits out better PE binaries than its predecessor
I dropped a binary into reversmode
... and gathered the imageinfo.txt + Sxxx output and dropped them into the dumped ROM\MODULES\filename folder, overwriting the originals
Any guidance would be appreciated.
// twitter: @WithinRafael
Sorry for getting everyone excited, I found the error in my ways. I wasn't aware (until now) that the binaries spit out by dumprom.pl are automatically decompressed. I used XIPPort to recompress my binaries (and fished them out of a folder relative to the executable).
Boots fine.
On a separate note, I'd like to rally everyone together and start getting better configuration management of this stuff. From what I've seen, these tools are spread out all over the damn place. Worse, the developers aren't including versioning information. I'm going to draft up some ideas on addressing the confusion and create a separate post.
WithinRafael said:
Sorry for getting everyone excited, I found the error in my ways. I wasn't aware (until now) that the binaries spit out by dumprom.pl are automatically decompressed. I used XIPPort to recompress my binaries (and fished them out of a folder relative to the executable).
Boots fine.
On a separate note, I'd like to rally everyone together and start getting better configuration management of this stuff. From what I've seen, these tools are spread out all over the damn place. Worse, the developers aren't including versioning information. I'm going to draft up some ideas on addressing the confusion and create a separate post.
Click to expand...
Click to collapse
yeah you may want to just start a thread with consolidated dumping/porting tools for these ROMs so we don't have to easter egg hunt