Database Info

Rom cooking on Vox

Hi all, I've been trying for quite some time to cook my first rom. I've now read a lot on the subjects here on these forums but it seems the vox is not the easiest device to start with I've successfully extracted all files from an .nbh rom upgrade. I've then extracted everything to /dump folder using prepare_imgfs.exe and imgfstodump.exe. Here I can delete/change/add files in the directory and rebuild the rom with buildimgfs.exe but it is not a very clean cooking... I'd like to be able to use Package tool. Actually I can use it and get the two folders /OEM and /SYS but then I really don't know how to rebuild the rom using Buildos.exe. Does anyone know how to do this ?
Tell me if my english is not very understandable..

I've finally been able to use these tools after a lot of trials and errors. But there is a lot of fixing to do in the building process. For exemple after running OEM and SYS folders through BuildOs a lot of files are missing in temp\dump
It seems every important file is missing in each of the subfolders. Missing dll's, missing exe's...
For example if I look in the zlib.dll\ directory I can see 5 files : imageinfo.bin, imageinfo.txt, S000, S001, S002, S003 BUT no zlib.dll ?! So I have to manually reimport those files... Is this a known issue with buildos and if so is there any solution to it ?
Thanks for any help

My bad, just realised reimporting the dlls is not at all needed
Still speaking alone ?

Perhaps this thread from the Kaiser forum helps you.

Dr Gonzo.... i would have lied to said something but my knowledge of cooking ROMs is zilch.... but i was hoping someones cooks a ROM for the Vox ... so wanted to ask u how its going?

I've been able to build an awkward "kitchen" for the Vox but I don't know yet if the roms built with it are really stable. Awkward because I don't really know how to write batch files and because I had to add a .dsm taken from Bepe's kitchen for Buildos.exe to work (but I delete it once the dump folder is rebuilt). But I have been able to add/remove packages and it seems to work.
I am currently building my rom from the Arabic one with smarttoolkit included, custom system screens, commanager and homescreen, office and HTC audio manager removed, windows live updated, Jbed instead of Jeodek etc... It seems to be stable but some things don't work yet (I still need to edit the registry)
But what I'd really like would be the possibility to add Bigstorage to the rom as it increases free memory from what I've read.
Maybe I can release this kitchen with some instructions and someone better than me could improve it ?

RE
Yeah that would be awesome to get some Vox Rom cooking happening when can you post your kitchen?

I'm in the process of writing a quick guide to go along my very dirty kitchen to show how to use it. For the moment only with HTC_Vox_ARA_1.27.415.4_4.1.13.47_02.98.90 as a base rom because I haven't tested anything else yet.

A few questions to all you chefs out there

I have been toying with the idea recently of brewing a ROM that is entirely my own, something that fits my needs perfectly. However, I am having trouble figuring how to go about doing so.
1. Basically, what I want to do is to start with a stock AT&T ROM, strip everything out of it, then only add back in what I use. It would seem simple enough, however what gets me is that when I extract the AT&T ROM, most of the applications seem to be contained within the OEMAPPS folder, with no simple way to sort through it. Sure I could just delete the folder and re add what I want, but thats not exactly what I had in mind. I would really like to pull out all the apps from that folder into their own individual folders so that I can keep anything if I feel like it while not having to keep everything. Does anyone know how to do this, or if there is any way other than doing it manually?
2. If I want to have registry tweaks installed on the ROM, what is the best way to go about doing so?
3. I have been searching and searching, but I cannot seem to figure out where the image that appears after the device splash screen is stored. Can someone point me in the right direction? I know Alex has his own custom image. EDIT: I am referring to the Welcome Screen.
4. When I previously cooked ROMs using the kitchen, it seems to retain the version number of the ROM that I based mine off of. Does anyone know the reason for this?
Yeah, a lot of questions I know, but once I get my ROM finished, I'll be sure to release it here.

Best thing I can recommend to you is try Alex's ROM Cooking tutorial. His ROM is AT&T ROM stripped. All apps are in OEM format so you can re-add as needed. The process of stripping the OEM apps is complicated and you need to find all files associated with a certain program.
Alex already did this so why do it again? You get a fully stripped ROM.
For the registry tweaks take a look at the OEM Packages included with Alex's ROM Cooking tutorial. There are several registry tweaks he has included so you can take a look at it and create you own from that.
The splash/welcome screen is called welcomehead.96.png. It's in the \Windows folder. You can cook your own by replacing the file in "SYS\Redist_dpi_96_resh_240_resv_320" folder if you use Alex's ROM tutorial. It's probably the same for other ROMS if you extracted your own but I haven't tried this. I replaced it so each time I create a ROM it's already there.
As for the ROM version you can change it (I think). In the OEM folder there's an OEMVERSION that contains a .provxml file. You can edit that and you'll see a version number.
Hope that helps.

Right, I know Alex has already released a completly stripped down version, but I really just want to cook something entirely of my own. Not that I dislike Alex's package, but I really would just like to do the work entirely by myself so that I can know all of the changes that were made, and how they were done. It gives me the kind of flexibility that I would like. Also, Alex has made some of his own changes to his UltraClean, so I don't have the level of control that I want.

Duplicate ROM Dump

Is this possible to dump your entire device with radio, OS, and settings stored -- into a RUU?
I've done a lot of customizations and installed various programs and a few friends want a copy of what I've done.

Newbie needs help with doing a small change to an existing ROM

I read the guides in this website, but need some extra guidance of how to achieve the following (if it is possible):
Let's say that one of the chefs cooked a ROM that I really like (let's call it "ROM X"), but there is one change that I would like to do to the ROM, for example, let's say I would like to delete the OEM package for the dialer that he used, and use an OEM package for a different dialer.
I understand that I need to do the following:
1. First I need to flash "ROM X" to my kaiser.
2. Now I need to dump "ROM X" from my kaiser, to my hard drive. At the end I get the 4 raw files.
Now comes the stage I'm not sure how to accomplish: I want to load the cooking applet of the kitchen software, and have all the database from the 4 raw files (of "ROM X") appear, so I can make the needed change in the OEM package, and continue to create the ROM. I understand that I need to somehow extract the information from the raw files, to something that the cooking applet of the kitchen software could use, but I'm not sure how...
Can anyone provide a bit of guidance ?
Thank you very much.
Btw, I've seen the following thread which deals with how to reconstruct a dumped ROM, but it doesn't deal with how to make changes to the ROM during the reconstruction process, rather the ROM you create, is simply a 100% duplicate of the ROM you dumped, and this is not what I'm trying to achieve...
http://forum.xda-developers.com/showthread.php?t=337066

Rom Files

Hey guys im trying to build my own rom using a tutorial i found on this site. the thing is that im at the section where im suppose to put the missing files where they r to go but i cant seem to get pass that section.
my problem is that the PKG Tool shows me the missing files, but where do i find them using the explorer window opened.
i am frustreated man and really need help.

Tambuyeye said:
Hey guys im trying to build my own rom using a tutorial i found on this site. the thing is that im at the section where im suppose to put the missing files where they r to go but i cant seem to get pass that section.
my problem is that the PKG Tool shows me the missing files, but where do i find them using the explorer window opened.
i am frustreated man and really need help.
Click to expand...
Click to collapse
When creating packages with Package tool it creates the following folders:
SYS
OEM
Missing <-- Thats what you are looking for.
I suggest that if this is your 1st attempt and you are building based on a custom rom, use HyperCore Kitchen. Its very easy to use and does the extraction much quicker and easier than doing it by hand. Once you have the hang of it then just move your stuff to another kitchen. Nice part about HyperCore you can dump just about any rom if you set it for that specific device. Just a note: some cookers protect their roms and you end up with almost everything in Missing. You can dump WizFlo from 6.1.1.3 upwards easily

When you have run the PkgTool - Build Packages option, don't mistaken the Missing Manifests for the same thing as Missing Files or Missing Packages. The missing "dsm" manifest files the Pkg Tool refers to are contained in the XIP files (which you will be doing next, i.e., extract XIP). So, you can just ignore the Missing Manifest message and continue on, however be aware that you must use compatible XIP that contains these "missing" dsm manifest files when you go to re-build your rom.
If there are indeed missing packages or missing files, it will tell you exactly what they are and where (what folder) they are supposed to go into. These missing packages/files will be in the dump folder along side the OEM and SYS folders after you run the Build Packages option in the PkgTool app.
This took me a while to realize as it was not explained (or at least I did not see it anywhere) in the various forums/threads on rom building.
If I am wrong on any of this someone please correct me as I too am relatively newbie to this and still learning.
Good Luck!