Gentlemen,
There is a wonderful amount of kitchens available for people to use however; the instructions are varied and confusing, especially if you are new. I have read many manuals on cooking ROMs and they all seem to be for a more experienced cook, and not a n00b. I have unlocked, and flash my HTC wiz200 myself by reading the threads, but I cannot wrap my head around a lot of the instructions poster by the great chefs we have on this site.
Is it possible for an experienced cook to produce a well put together manual for all to understand? The instructions I have read are based a lot on the assumption that the reader is well versed in the understanding and mechanics of a ROM. That is to say they have experienced extracting files, creating CAB files and, most importantly, the way a ROM needs to be structured with HKEYs and the like.
I truly believe that the community has an opportunity to expand the quality and diversity of the ROMs in the world by putting together a concise instruction manual.
I may not be the sharpest tool in the shed, but I’m not a box of rocks.
Actually, most of the ROM kitchens are not near as complicated as you think they are. In most of the kitchens (can't say all since I haven't tried all of them) you don't have to do any of those things that you mentioned. I have my own cooked ROM and I don't know how to do any of those things either. The only time you do have to do that kind of stuff is if you decide to add something that doesn't already exist in the kitchen and since most of them have pretty much anything you'd want in them, if there actually is something else you really want it's a lot easier to install it after you've already cooked your rom and flashed it to your phone.
Personally, this is my favorite kitchen and the one I cooked my most recent ROM with - http://forum.xda-developers.com/showthread.php?t=311144.
You'll need to pick a ROM and an OEM version and then download and extract them to the same folder and then click on the exe that says Build OS and it will let you pick and choose what you want to add to your ROM.
That will get you started, but there is a little more to it (nothing difficult at all), but the instructions are on the kitchen page anyway. I'd detail more, but I just realised I'm going to be late for work if I do. PLay with that for now if you want and if you have any more ?'s I'll try to answer them for you after work if someone else hasn't already answered them.
xeno1 said:
http://forum.xda-developers.com/showthread.php?t=311144.
PLay with that for now if you want and if you have any more ?'s I'll try to answer them for you after work if someone else hasn't already answered them.
Click to expand...
Click to collapse
LOL that's one of the kitchens that i have tried. And the reason i want to know more is because i do want to add programs into the ROM saving so space.
It seems that there are other people interested in clear instructions as this thread has been viewed quite a bit in the short time i have posted it.
If you've come to this thread looking for clear instructions, please make a post of "instruct me" so the cooks will know how much of a need there really is.
And thanks for adding your assistance, should i need it.
xeno1 said:
Personally, this is my favorite kitchen and the one I cooked my most recent ROM with - http://forum.xda-developers.com/showthread.php?t=311144.
You'll need to pick a ROM and an OEM version and then download and extract them to the same folder and then click on the exe that says Build OS and it will let you pick and choose what you want to add to your ROM.
Click to expand...
Click to collapse
This is the kitchen i was looking at i downloaded all the files it says to download and i clicked on build rom.. but theres a lot of things on there that i can choose to have and not.. but theres a lot of this i dnt know wat they are or wat they do.. and than ive been trying to get ride of Arcesoft SMS and i cant.. and i downloaded the tmobile applications from the post.. but i dnt know wat to do with that either.. that's y i need good instrutions...
ps. instruct me
Give me a little time to see if I can't remember how to add apps into the kitchen. It's been a few months since I've done that kind of thing and I don't quite remember exactly how to do it. If I remember right it wasn't too excessively difficult. It's a whole lot easier just to use what's already included in the kitchen and then add other things by cab file afterwards though.
I'm not really sure why it would save that much space cooking it in to the ROM rather than adding it by cab, especially if you delete the cab file afterwards or move it to your SD card. The ROM I just cooked ended up having more than 44 Mb of program storage left afterwards and even after adding everything else that I wanted, it still has more than 32 Mb left.
I know what you mean when you said that there were some things in the kitchen that you didn't know what they were to know if you wanted to add them or not smileyaj2005. The things that I wasn't sure what they were I just googled for and found out what they were and whether or not I wanted to add them.
BuildOS.exe
xeno1,
here's another reason to have a clear manual:
Is anyone getting the following applicaion error, or know how to solve the following:
BuildOS.exe - Application Error
The Application faild to initalize properly (0x0000135). Click on OK to terminate the application
This is from the kitchen you recomended.
I too have been tinkering with cooking for several devices (the wonderful Hermes, the useful Herald, the workhorse Wizard and the good old Prophet) and while I've been successful in creating ROMs, there is a lot that I would like to understand better... I've searched but I've not found sufficient info in the time I've had to gain a full understanding.
I'm keen to first understand and then write a wiki guide to the structure of ROMs, the steps in going from an image to the individual files and back, how packages are built, etc. While much of this info exists, it's scattered all over this site and very difficult for people with limited time to find.
Also, this works needs much help from the chefs here. Would one or two of them volunteer to help me write all this up in a manner that makes everything clear to the tech savvy beginner?
I've gained much from this community and want to do something useful in return. And since my forte is technology and I can write well (I think!), I hope that I can make a Wiki Guide that will be useful to all.
Oh great chefs! Do we have some volunteers who can help us in this task?
SayMobile said:
I too have been tinkering with cooking for several devices (the wonderful Hermes, the useful Herald, the workhorse Wizard and the good old Prophet) and while I've been successful in creating ROMs, there is a lot that I would like to understand better... I've searched but I've not found sufficient info in the time I've had to gain a full understanding.
I'm keen to first understand and then write a wiki guide to the structure of ROMs, the steps in going from an image to the individual files and back, how packages are built, etc. While much of this info exists, it's scattered all over this site and very difficult for people with limited time to find.
Also, this works needs much help from the chefs here. Would one or two of them volunteer to help me write all this up in a manner that makes everything clear to the tech savvy beginner?
I've gained much from this community and want to do something useful in return. And since my forte is technology and I can write well (I think!), I hope that I can make a Wiki Guide that will be useful to all.
Oh great chefs! Do we have some volunteers who can help us in this task?
Click to expand...
Click to collapse
I'm right there with you. At my job i'm currently macking training guides that are easy to understand, even if you've never heard of them before. It's quite the task but, it benifets everyone.
evangelious8152 said:
BuildOS.exe - Application Error
The Application faild to initalize properly (0x0000135). Click on OK to terminate the application
Click to expand...
Click to collapse
You need to update your .NET framework. Just run windows update or download the newest version from Microsoft.
I'm still working on how to add software to your kitchen. I'll figure it out sooner or later though. It might actually be faster if you just ask mfrazzz, mattk_r, or farria themselves in one of their kitchen threads. I'm in no way claiming to be a great chef of any kind, I've only cooked a few ROM's and those were from kitchens one of those "great chefs" built. I will still do my best to figure out how to add apps to the kitchen though and let you know.
Notice: this information is for Wizard kitchens only as I don't know if it will work in any other type of kitchen. This thread should actually be in the Wizard forum, but I didn't start the thread. All those following it, if it disappears from this forum, which it probably will, try to find it there.
Ok, here's what I've got so far on how to add your own apps to the kitchen:
First, you have to install the app on your phone in whatever OS you're using now.
Second, you then have to extract every file from your phone that it just installed and put it in a folder on your computer.
Third, extract all of the registry keys that it installed. For now, just put them in a txt file in the same folder. Later you will need those keys to create a .rgu file.
Thanks to meschle (and BenThon, the creator of this app) you can download this app - http://www.codeppc.com/telechargemen...nf/msceinf.htm and it will extract any .cab file into a file on your computer that you can use instead of having to install it to your ppc and then finding all of the files as in the first 2 steps. It will also show you the registry keys so you can copy them in to the .rgu file instead of having to go through your registry and finding them as in the third step.
Now, go to http://www.famkruithof.net/uuid/uuidgen and get a GUID. As soon as you go to the page one will be generated for you at the top of the page. Here's one that was generated for me 04987fe2-31a8-11dc-8314-0800200c9a66. You might want to copy that in to a txt file for your use later. You will need to get a new GUID for each app that you want to add to your kitchen.
Next, create an empty txt document and name it (your GUID) 04987fe2-31a8-11dc-8314-0800200c9a66.dsm (note that that is my GUID, replace it with your own). When saving that file, choose Save file type as All Files.
Then create another txt document. In it you will type in it REGEDIT4 then [enter] and then copy and paste the registry keys in to it that I told you to save earlier. After the last line of the registry keys there needs to be a blank line so at the end of the last line of registry keys hit [enter] and then [enter] again. Save that txt file (your GUID) 04987fe2-31a8-11dc-8314-0800200c9a66.rgu and save it as file type UNICODE. (Note) If your app doesn't have any registry keys, which some apps don't, you can skip this entire step completely.
Almost there.
Now, you need to create a link to the app so that it shows up under the programs menu. More than likely if you extracted all the files from your phone that the app installed there will already be one so you wont need to. If you do though, create another txt document and type in it #"\Windows\yourappsnamehere.exe" and save that as yourappsname.lnk and save as file type All Files.
In another new txt document copy and paste this:
Directory("\Windows\Start Menu\Programs"):-File("yourappsname.lnk","\Windows\yourappsname.lnk")
Save this one as initflashfiles.txt and save as file type UNICODE
Last step, create one last txt file and copy and paste this in it:
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<Items>
<Item name="yourappsname" group="My Apps" checked="false">
<Tip></Tip>
<Guid type="p">04987fe2-31a8-11dc-8314-0800200c9a66</Guid>
</Item>
</Items>
Make sure you put your GUID in instead of mine that's in there now, and put your apps name where I put yourappsname and make sure you leave the "" in there. Save this file as option.xml and save as file type All files. If you want to add a tool tip description, just type it in between the <tip></tip> and when you move your mouse over it in the BuildOS app it will show up.
I forgot, one last thing, put this entire folder in to the OEM folder in the kitchen and you're done.
Run BuildOS and there should now be a new categorie called My Apps for you to select the apps you just worked so hard to put in there.
I don't think I missed anything, but if any kitchen builders or cooks see anything wrong, feel free to let me know. Also, if anyone knows how to extract the files and registry keys straight from the cab file itself I'd be more than happy to learn how to do it.
P.S. I told you that it was easier to just add it as a cab file afterwards.
The whole point in cooking built-in apps is to preserve the limited persistent storage. If storage is not a problem with you, then you are better off installing cabs...
cheers,
Jiggs
kitchens sux
xeno1,
i've been playing with 4 different kitchens, and i'm lucky if i get the core rom to flash. most of these kitches come up with one error or another in the ms-dos shell. it is nuts trying to figure out how these "tools" work because no one wants to produce a good manual.
we are all here because what we get from resellers doesn't fit out needs and we don't want to be stuck with their crappy branding. however, my experinces with these kitchens is no diffrent. these kitchens are "locked" to only work (sorta and sometimes) with whatever their creator puts out. i guess we will soon see websites on how to "unlock" these kitches.
Did the instructions that I spent hours going through everything to find and then explain not work? They worked in both Farria's kitchen and doubleofours kitchen when I tried them.
xeno1 said:
Did the instructions that I spent hours going through everything to find and then explain not work? They worked in both Farria's kitchen and doubleofours kitchen when I tried them.
Click to expand...
Click to collapse
i'm talking about the kitchens not knowing where to look for files that are in placed. sorry for the confusion.
As long as you put them in the OEM folder and and you create the option.xml document it should find them and add the option to the kitchen. If I remember right, if you don't create the option.xml document it won't show up in the kitchen, but it will still add that file to your cooked ROM automatically.
Hi xeno1 - I find using MSCEInf by BenThon http://www.codeppc.com/telechargements/msceinf/msceinf.htm very good for extracting files and inf and _setup.xml files from cabs. I add the registry info from here into default.rgu and away you go.
One thing you forgot to mention concerning initflashfiles.dat - if you edit it using notepad you must delete the first 2 entries with a hex editor or U will get errors. (actually phone will not boot at all ) Use Editpad lite (or others) and you dont need to do this step.
Thanks meschle, MSCEInf will come in really handy.
I just have one question though, you mentioned the initfiles.dat, I've never seen this file in any of the folders in any OEM package and none of the cooks mentioned it in any of their posts on how to create new packages. Where is it located, so I can take a look at it? I s it possible that this isn't part of cooking a wizard ROM? Like I put at the top of my post that has the steps, this thread really should be in the wizard forum.
Opps my mistake i was in a hurry.
I meant initflashfiles.dat lol
That's ok, that's not a big deal. I did however go back and re-read farias post and noticed that I did make a mistake in the initflashfiles. Faria said to save it as UNICODE, so I changed that part. He says to save it as initflashfiles.txt though, not .dat. I also went through a bunch of initflashfiles and realized that most of that stuff that I copied and pasted there was just comments, and that all you really need is -
Directory("\Windows\Start Menu\Programs"):-File("yourappsname.lnk","\Windows\yourappsname.lnk")
Does that still need to be edited in a hex editor?
I greatly appreciate your help.
xeno1 said:
That's ok, that's not a big deal. I did however go back and re-read farias post and noticed that I did make a mistake in the initflashfiles. Faria said to save it as UNICODE, so I changed that part. He says to save it as initflashfiles.txt though, not .dat. I also went through a bunch of initflashfiles and realized that most of that stuff that I copied and pasted there was just comments, and that all you really need is -
Directory("\Windows\Start Menu\Programs"):-File("yourappsname.lnk","\Windows\yourappsname.lnk")
Does that still need to be edited in a hex editor?
I greatly appreciate your help.
Click to expand...
Click to collapse
Even if you do the initflashfiles.txt method (in unicode of course) FF FE are placed infront of 3B which is what the first entry should be on the hex editor so FF and FE need to be deleted. Best way i find is use editpad lite - enclosed.
Try it you'll see.
(was HTC greloc? help)
Hello!
I am working towards a flashable rom for a number of devices to allow use of the internal memory for android (kaiser, polaris, nike, vogue, etc)
What tool is used to partition the flash device? How do you turn on or off the extended rom partition, and could this method be used to set aside 80-120MB of space as a separate partition on the flash, for use by android?
Any help is appreciated!
Thanks!
You see, a typical wm5/wm6 rom is a disk image, with MBR and other traditional stuff. Usually, the bootloader calculates the size of storage area based on the size of the OS image. Not sure you can add an extra partition after rom and storage, but you could create a new partition in the OS part (a typical rom has 2 or 3 partitions, uldr, kernel and imgfs, respectively, so there is one empty 'slot' in the mbr) and let android use it or put android partition to ExtROM.
and yeah, g'reloc is a tool for patching wince binaries to change their virtual addresses, nothing to do with partitioning
great!
So can I just use, for example, fdisk on the .nbh file? or is it on the .nb? I'd be happy to use the extrom for the android partition, just need to set it to 100MB instead of 10...
Or do I need to create a dummy ExtROM.nb file that is the right size with a signature of 900?
Hey ya'll, I have a simple question.
I want to know if I can flash the ext rom from another HTC device onto my BA ext rom?
I just installed the 142 Tmo Uk rom, and was curious if I can grab the ext rom off of another Tmo USA device, so I have all the right settings and stuff?
TIA!
i wouldn't think so. may be able to do it, i wouldn't attempt it. i stripped my extrom, they don't actually have anything useful in them. just horrible themes and bad software.
you however could probably extract the extended rom from another device and copy the files and manually install them. that'd be easy enough i think.
yeah, flashing a rom from another device is not such a good idea, but since you are using wm2003, you can visit -=this tutorial=- and gain another 16mb of storage space and then just copy cabs that you want to the device or maybe even build you own extrom, to be copied to the sd card and installed automatically. to find out how that is done (actually pretty easy!) just use forum search and look for "cfg.txt" and Chef_Tony. i wrote some pretty long tutorials about that.
basicly it is just making an automated install routine for your most commonly used programs, so whenever you hard reset your device, the programs YOU want are installed, not those ridiculous t-mobile customizations, their pink dialer skin and things like that.
EDIT: btw. you should never take an entire extrom of another device. you never know, if maybe some of the things installed by the extrom are dependant of the display resolution or use device specific interfaces or mess around with device specific hardware buttons or drivers, you should extract the cabs and google their names, if you are not sure, what that actually does, so you can be sure, it will work on your blueangel!
have fun with that.
and @cerjam: don't be offended, your answer is completely right, i agree, just wanted to add a few little things
Perfect answers!
So, chef_tony, your telling me that it's ok to merge my extrom and storage in wm2003se? and then copy my cabs and write a cfg.txt of my own for an sd card?
I realize that I should do all the reading, but I'm the kinda guy who needs a generalized big picture before I start ripping apart all the details, so I'm looking for **** and jane/oversimplified answers.
Thanks, guys (and gals, if you are one)
Hi all,
I have an ASUS R600 GPS running WinCE 5.0 core. I unlocked it using AsusPocket (ASUS customized version of MioPocket to keep things such as bluetooth) and everything seemed fine.
However I'm running against a "low memory" errors when running certain navi software such as Navigon and iGo. The device has 64 Mb of RAM which should be plenty for these, as my cheap Omnitech has the same amount and has no problems.
With help of MioPocket guys, I traced it down to a massive \Windows in this device's ROM. It is like 25 Mb as they dumped not only every dll they could find there, but also eg a lot of big wav and bmp files. Couple wav files are close to 1Mg each! Since according to these folks \Windows just gets copied from ROM to RAM on startup, I end up with far less free memory to play with than I'd like.
I'm new to ROM cooking but with some help I'm sure I could do it. To keep things very simple I was thinking of just replacing these big wav files with a small one. This way the file count and names wouldn't change and I wouldn't run a risk of ever running into a "file not found" condition. I really don't care if on startup the device plays a simple "ding" as opposed to 20 sec sound. Since soft that I want actually runs and only gets into low memory condition on more complex route recalculation or reality view screens, I think this would be enough to get me over the hurdle. Of course, any checksums will need to be regenerated as needed.
So, at this point I have downloaded upgrade ROM images for this device. Is that something that can be disassembled, modified as described above, and put back together? I tired naively unleashing dumprom on one of these .bin files, but got back "unable to determine loading offsets" error. I guess I shouldn't be surprised as at this point I don't know what I'm doing...
Can anybody offer any help to me? With all the amazing things I read on this site people doing with ROM modifications, it looks like what I'm trying to do should be a walk in the park. Am I right trying to go from upgrade .bin file? Or should I get some tools to read off the device? Please help.
Btw. if anybody'd like to peek at this upgrade bin, it can be downloaded here: hxxp://support.asus.com/download/download.aspx?modelname=R600&SLanguage=en-us, in the firmware section, version 4.3.0 and version 4.8.0 for NA users. Unfortunately no direct link.
Thanks in advance
mamon