Database Users

Needed visual kitchen for ELFIN

plz someone fgure it out.we r in neede for this best kitchen..plz...for elfin.

Hi saurabh88!
Just download the latest shiped rom you find, and dump it with visual kitchen.
Then you can edit your and change OEM/XIP/SYS/EXT.

sandman01 said:
Hi saurabh88!
Just download the latest shiped rom you find, and dump it with visual kitchen.
Then you can edit your and change OEM/XIP/SYS/EXT.
Click to expand...
Click to collapse
first of all thanx my dear friend for the guidance.so if i had visual kitchen for gene and if i dump shipped rom from elfin then ihave had elfin kitchen na!am i right...

Correct!
After dumping an original Rom you have a base kitchen which you can modify step per step.
Download new Base drivers and replace the old.
Replace XIP/SYS with current one (be careful at the moment no native elfin kernel is available so do not set Real WM6.5 AKU)
...
..

i done made the rom but when i flash it it goes u to 89% then says unable to update,follow the imstr. to recover your device.plz help me.

THIS HAPPEN;
after downloading vk from the link u have given and dumping again my rom when i click to select my device while cooking it says me
"os value on NBHUtil.xml for elfo1000 not found.....set 0*4000 as default"
what is it mean?does it affect my rom?

After Dumping an original *.nbh file save the configuration.
That are the right settings for reflashing your Elfin.
I'm not sure if the OS id. effects your rom, but Chunk Size for elf(in) must set to 1024 (acording to nbhutility).
I do not have my Elfin anymore, so I cant test different settings.
At first download a cooked rom and flash it to get a working device. Or download the latest shiped rom from your provider. Than start dumping ant flashing again to see if the error is still there.

i done using shipped rom....chunk size is ok but now i m stucked at smart mobility.this is also happen with bepes kitchen.
one more thing if i flash shipped rom anything will be wrong?will it brick my device?

[SOLVED] Missing Icons In Start Menu

Hi 2 all chefs and developers..
I am using evk latest kitchen to cook a rom. I Have dump of stock 1.66 and 1.72 stock roms..
As 1.72 is a t-mobile branded rom.. i dont want to use t-mobile branded rom.
Ext packages and its itz upgraded HTC MESSAGING client and manila from 1.72 rom i want to cook them with 1.66 rom.
I simply copy and paste the said packages from 1.72 rom to 1.66 EXT folder and then run the Kitchen.
Rom cooked ok. and it flashed ok without any error.
but the problem is..Some of the icons.. ie: Tools, mails, multimedia etc etc goes classic . and applications icons from them comes out in the start menu.
i dont know what i am doing wrong?
kindly advice what to do.

you need to have the initflashfiles.dat entries for pkgs you bring over from 1.72, not just copy and paste the pkgs.

twopumpchump said:
you need to have the initflashfiles.dat entries for pkgs you bring over from 1.72, not just copy and paste the pkgs.
Click to expand...
Click to collapse
thx 4 ur reply
how to bring that initflashfiles.dat???? just copy paste from 1.72 rom or have to edit it??? if have to edit that file then how to do it??

mon_money said:
thx 4 ur reply
how to bring that initflashfiles.dat???? just copy paste from 1.72 rom or have to edit it??? if have to edit that file then how to do it??
Click to expand...
Click to collapse
you could copy over initflash.dat from the newer rom
you can find it in kitchen>oem>device>0409>oem_lang_0409
as said you could also edit the initflash manually
by rightclicking on the initflash.dat file and select open with notepad(not sure ifits called this way but its the second option

miniterror said:
you could copy over initflash.dat from the newer rom
you can find it in kitchen>oem>device>0409>oem_lang_0409
as said you could also edit the initflash manually
by rightclicking on the initflash.dat file and select open with notepad(not sure ifits called this way but its the second option
Click to expand...
Click to collapse
__________________________________
Thanks.. it is working now..
Problem Solved..

[SOLVED] Enabling 576MB in TMOUS HD2

Hi,
I've done research on the forum here and found that to unlock the full 576 RAM in HD2 you need two things from the TMOUS ROM. The Radio and nk.exe. I've managed to download the appropriate Radio to unlock the memory but cannot for the life of me understand how to get the nk.exe.
I am using osKitchen Kitchen v1.25 to cook my roms. It uses the following structure under the Sources folder:
EXT
MSXIPKernel
NK
OEM
Other
ROM
SYS
Replacing the NK folder in the TMOUK kitchen from the TMOUS ROM simply does not work the resultant ROM does not boot and just hangs the device.
Could one of our chefs please explain how to port the nk.exe from the US build to unlock the memory in the T-Mobile UK ROM 1.72.
Using the following 576-enabled Radio
RUU_Leo_Radio_15.34.50.07U_2.08.50.08_2
Many thanks in advance
Mod edit: SOLVED

thecrater said:
Hi,
I've done research on the forum here and found that to unlock the full 576 RAM in HD2 you need two things from the TMOUS ROM. The Radio and nk.exe. I've managed to download the appropriate Radio to unlock the memory but cannot for the life of me understand how to get the nk.exe.
I am using osKitchen Kitchen v1.25 to cook my roms. It uses the following structure under the Sources folder:
EXT
MSXIPKernel
NK
OEM
Other
ROM
SYS
Replacing the NK folder in the TMOUK kitchen from the TMOUS ROM simply does not work the resultant ROM does not boot and just hangs the device.
Could one of our chefs please explain how to port the nk.exe from the US build to unlock the memory in the T-Mobile UK ROM 1.72.
Using the following 576-enabled Radio
RUU_Leo_Radio_15.34.50.07U_2.08.50.08_2
Many thanks in advance
Click to expand...
Click to collapse
For the 576MB patch you need only to replace these folders from an 2.07 or 2.02 Stock-Rom:
Rom\XIP\OEMXIPKernel\nk.exe
OEM\OEMDrivers
OEM\OEMDriversHigh
Then you need to replace again with this folder
OEM\OEMDrivers\ddi.dll
with an older Base than 2.07/2.02 (1.72 in your case is recommended)

patensas said:
For the 576MB patch you need only to replace these folders from an 2.07 or 2.02 Stock-Rom:
Then you need to replace again with this folder
OEM\OEMDrivers\ddi.dll
with an older Base than 2.07/2.02 (1.72 in your case is recommended)
Click to expand...
Click to collapse
Why ddi.dll ? mine works fine with new 2.13/2.11/2.10 ddi.dll

patensas said:
For the 576MB patch you need only to replace these folders from an 2.07 or 2.02 Stock-Rom:
Rom\XIP\OEMXIPKernel\nk.exe
OEM\OEMDrivers
OEM\OEMDriversHigh
Then you need to replace again with this folder
OEM\OEMDrivers\ddi.dll
with an older Base than 2.07/2.02 (1.72 in your case is recommended)
Click to expand...
Click to collapse
Thank you very much indeed for your kind help. It worked perfectly

Hi, I'm a newbie for ROM cooking, experienced cookers, please advise.
I'm using HD2/Leo phone, I learned how to use HSPL, flash a cooked ROM, so I'm start thinking of cooking the ROM my own, and what all I need is retain original 1.66 707.1 Asia WWE version of stock ROM, but only to enable 576MB RAM.
I found a kitchen, oskitchen zero 1.31, use the GUI and extracted the stock ROM, and stop here, because I don't know how to cook the ROM...
Experienced cookers, please advise, thanks in advance!!!

patensas posted like 2 posts up from yours which files you need to replace.

which means that i just copy all the folder need, then paste inside the osKitchen Zero folder, and finally click "Start building button" to cook my ROM...?

I also want to know why ddi.dll need to be remain old version?
OEM\OEMDrivers\ddi.dll

hello fellow chefs
i am trying to make a verry smooth rom in dutch for soem friends of mine
it is working out quite well but i want to enable the 576 ram tweak
in patensas his post he says i need to change things from a tmous rom
if i use the tmous 2.13.531.1 as base rom do i still need to change those folders?
thanks in advance

sorry to ask but coul some one upload the files to make the 576 mb tweak?
i have 2.13 tmous as base in the kitchen and it would save me a download and dump
thanks in advance

All you need is in the 2.13 TMOUS.

pkoper said:
All you need is in the 2.13 TMOUS.
Click to expand...
Click to collapse
then i dont get it:-o
i installed Leo_RADIO_15.34.50.07U_2.08.50.08 on the phone but no 576 mb tweak:S

Using 2.13 base you should have 576 anyway.
What did you change?

pkoper said:
Using 2.13 base you should have 576 anyway.
What did you change?
Click to expand...
Click to collapse
to be honest i have no idea why it aint working
when you got the settings tab and scroll down to device info
there you choose hardware info it should also say 576?
the thing i did is dump the tmous 2.13 rom with ervius
then i took out the 0409 folder in oem and replaced it with the the one i use for blackstone(maybe the fault is here) then i replaced the ext packages with the ones i use i blackstone kitchen(compared wich are unnesacary and left those out) and then recooked the rom
i also decided today that i am gonna rebuild the entire kitchen from scratch without copy pasting the 0409 folder in oem and set everything up from there and remake the initflash.dat the way i want it
i havent changed the ddi.dll so that might be the trick why it aitn working
on side note:
wish i whasnt in the middle of moving and had the actual device for a few days
that would definetly make things easier for me
ps: what do you think is the best base to use to build the kitchen on with ervius kitchen
tmous 3.14? it would sound logical that newer is better although there are differences between the american and european leo's

Hi all !
I'm trying to cook a personal custom rom I just want to change the build from 6.5 to 6.5.X of the official htc 3.14 italian rom. I would also like to enable the 576 mb of ram. I have already installed on the phone the 2.15 radio, what files I need to change inside the kitchen ( I use oskitchen ) ? I have a t-mobile.uk hd2 ( I have bought it from england.
so I think that it's the european version )

light_n_roses said:
Hi all !
I'm trying to cook a personal custom rom I just want to change the build from 6.5 to 6.5.X of the official htc 3.14 italian rom. I would also like to enable the 576 mb of ram. I have already installed on the phone the 2.15 radio, what files I need to change inside the kitchen ( I use oskitchen ) ? I have a t-mobile.uk hd2 ( I have bought it from england.
so I think that it's the european version )
Click to expand...
Click to collapse
Take the nk.exe(from oemxipkernel) from 2.13 tmous.I think also the nk.exe from 3.14 tmous should be ok but I havent try it.

Could someone just post an attachment with the modules needed to enable the extra RAM? I'm sure it would make it easier for everyone. I'd do it, but I don't have an hd2.

Farmer Ted said:
Could someone just post an attachment with the modules needed to enable the extra RAM? I'm sure it would make it easier for everyone. I'd do it, but I don't have an hd2.
Click to expand...
Click to collapse
The way that the European Leo device gets the 576 ram enabled is the following:
Replace the nk.exe with the nk.exe from TMOUS rom (in Sources\Devices\HTC Leo\Profiles\default\OEMXIPKernel folder for oskitchen, or \ROM\LEO\build number\OEMXIPKERNEL for ervius kitchen).
I attach the 2.13 tmous and 3.14 tmous nk.exe modules.Both do the trick or enable the 576 ram (for those who believe it).
Personally in my Leo I didnt see any difference with the 576 ram enabled.

How to build a new WM6.5 rom base on WM6.1 ship Rom?

Hi all,
I try to cook rom for my device Samsung M490. I have a Ship rom in Korean language(0412) ( i cannot find the English one).
I build with new WM6.1 SYS/XIP (lang 0409) , the device boot ok, the language changed to Eng, but the setting shortcut not work. I cannot set the rington.
I build with new WM6.5 SYS/XIP (0409) and it cannot boot, the screen turn off after the Anycall logo appear.
Now can you ask me how to make it work with W6.5 build? what thing I will do, what file/folder will be change/edit?
My ship rom here:
Code:
211.189.38.83/umsvcbin/SCH-M490/SCH-M490_CI24_pda.bin
I do follow as below:
-Take out the XIP.BIN form a WM6.5 Cooked by chinese guy an use it as DEVICE_BINs , use a new build XIP.BIN (23662) as DONOR_BINs and use Xipkitchen to make a new XIP.BIN out.
-Dump Ship 6.1 rom, replace SYS by new wm6.5 SYS build (23662), repalce initflashfiles.dat by English one. add XIP.BIN out above into file OS.NB.
- Copy os.nb to \ROM, copy \SYS, \OEM, \ROM into kitchen an run.
- It is still not boot, please advice anything else to to?
Thanks very much for your help

There is too little info here to help you. Does your device have a native 6.5 kernel? You will need to have one to be able to flash a 6.5 ROM and make it work on your device.

You mean ''oemxipkerner''? .Samsung didn't release the wm6.5 rom. but i found some cooked wm6.5 rom in Korean and Chinese. can I take it from these rom?

I dont think so. You will first need to dump a stock rom provided by Samsung for your device. Then replace the oemxipkernel with a patched one, which has a 6.5NK.

I dump a ship rom already, I use XIPkithen to make a new xip.bin from a new wm6.1 release, the device boot ok , I do the same way with build wm6.5 but the device can't boot. where can i find a patched oemxipkerner?

You will have to search for it. You will need a 6.5NK for WM 6.5.X to boot on your device.

If Samsung has not released a stock 6.5 ROM for your device, chances are you wont have a native 6.5 kernel.

If you don't have a native 6.5 kernel, you need to recmod a lot of files/folders. This thread @ Mobile Underground has lots of good info.

You said you dumped a stock 6.1 ROM. In this ROM, see if you have a 6.5 Native Kernel by dumping xip.bin. Open nk.exe/s000 in a hex editor. Search for the ASCII string "platform". Near this string there should be the build number that this nk.exe was compiled against.
WM 6.5 builds began around 21100. WM 6.1 and previous builds will be <=21058.

OsKitchen can import the ROM of that phone and also seems able to rebuild it correctly (but make sure the final file is correct for your phone since there are something like ten different BIN file formats) and since it can already suggest the packages to recmod it could also help with 6.5.5 porting if you don't have a 6.5 kernel (which you probably won't find anywhere: the only modded 6.5 kernels I've seen are for htc devices).

thank airxtreme, i use os kitchen before. I dump a Ship rom and build it again, flash rom to phone and it not boot. I try to use new Ervius kitchen but i don't know how to make file OS.NB.PAYLOAD. Now i try a old type Ervius kitchen (5.3).
I just do:
-Take out the XIP.BIN form a WM6.5 Cooked by chinese guy an use it as DEVICE_BINs , use a new build XIP.BIN as DONOR_BINs and use Xipkitchen to make a new XIP.BIN out.
-Dump Ship 6.1 rom, replace SYS by new wm6.5 SYS build, repalce initflashfiles.dat by English one. add XI.BIN out above into file OS.NB.
- Copy os.nb to \ROM, copy \SYS, \OEM, \ROM into kitchen an run.
- It is still not boot, please advice anything else to to?

theanh6 said:
thank airxtreme, i use os kitchen before. I dump a Ship rom and build it again, flash rom to phone and it not boot. I try to use new Ervius kitchen but i don't know how to make file OS.NB.PAYLOAD. Now i try a old type Ervius kitchen (5.3).
I just do:
-Take out the XIP.BIN form a WM6.5 Cooked by chinese guy an use it as DEVICE_BINs , use a new build XIP.BIN as DONOR_BINs and use Xipkitchen to make a new XIP.BIN out.
-Dump Ship 6.1 rom, replace SYS by new wm6.5 SYS build, repalce initflashfiles.dat by English one. add XI.BIN out above into file OS.NB.
- Copy os.nb to \ROM, copy \SYS, \OEM, \ROM into kitchen an run.
- It is still not boot, please advice anything else to to?
Click to expand...
Click to collapse
Which EXT packages are you using?

anand12 said:
Which EXT packages are you using?
Click to expand...
Click to collapse
I don't use any EXT packages.

theanh6 said:
...-Take out the XIP.BIN form a WM6.5 Cooked by chinese guy an use it as DEVICE_BINs , use a new build XIP.BIN as DONOR_BINs....
Click to expand...
Click to collapse
First of all - don't try to dump someones roms to get xip.bin or whatever!
Many guys, including me (does not matter - Chinese or not) - are deleting reloc sections and dsm files while building custom roms to save the space. So if you use such a xip - you will get non-bootable rom.
1. Take the latest OFFICIAL rom
2. Dump it to get original XIP and original OEM
3. Download new build that you want to cook.
4. Port new xip. Use the original XIP as donor of OEMXIPKernel and new xip from downloaded build as a source of MSXIPKernel & MSXIPKernelTLK
5. Take ported xip, OEM (drivers) from official rom, SYS from downloaded new build
6. Start cooking.

Very nice step by step explanation by Andrew. It doesnt get simpler than this!
The most important part - Dump the official rom released for YOUR device NOT for any other. You risk bricking your device.

Thanks AndrewSh & anand12 for your advice, i follow step by step but it only ok for a 6.1 build, and wm 6.5 fail to boot again.
Now I sucess to build an English wm6.5, my way is:
-Dump a cooked Korean ROM build 21815, I have \ROM, \OEM, \SYS, XIP.BIN.
-Remove all file/folder in \SYS but keep .ROM, .VM , Metadata, then copy all from SYS build 21815E(English-0409).
-add XIP.BIN above into OS.NB get from official rom an copy new OS.NB to \ROM.
-Now i have \ROM; \SYS; \OEM, copy them into kitchen an run. Flash new rom to phone and it work ok.
I try to cook a new ROM with last wm6.5 build, but i feel sad because it fail again.
Now i have some quesion, please spend a litle time to help me to clarify:
1. i think my problem is at "Metadata" folder. When we cook a new build, what will we do with "Metadata" (change all folder, change some file/folder or edit some thing) ?
2. I can not set the ringtone for my cook rom, both in 6.1&6.5 build. The "Ringtone" feild is empty as the picture i attached. What thing be wrong here?

Look you must have a 6.5 NK for your device. If not, you must recmod files. Are you doing that? Please be sure and clarify.

@theanh6: Can you upload your cooked here? Thank you very much.

Thank you all, It fully working now (with some small bug but no problem)
@Mrkid: Please send an email to me at [email protected] if you want to try this rom.

How can I make a rom that works both with T-MO & WWE LEO?

So, how can one build a rom that will work both on a T-Mobile HD2 and on the WWE HD2?
Should I try to work with the WWE stock roms and hope it will work with the T-MO or is there any specifics needs to be done?

I beleive my EVK Kitchen will do what you want...

rstoyguy said:
I beleive my EVK Kitchen will do what you want...
Click to expand...
Click to collapse
nice to point him in a ready to use kitchen but i think its handy if you type out what you have done to make it that way so other people can do it themselves as i think it are only a few files and its easier to change a few files then customize a entire kitchen to youre own liking

I take the OEMXIPKernel and OEMDrivers packages from a 2.1x ROM and use them as part of my ROM's base to make it 1024mb compatible. You could use the whole 2.1x OEM dir, but I find it unstable myself.

millski said:
I take the OEMXIPKernel and OEMDrivers packages from a 2.1x ROM and use them as part of my ROM's base to make it 1024mb compatible. You could use the whole 2.1x OEM dir, but I find it unstable myself.
Click to expand...
Click to collapse
Basically, you work on a WWE rom as the base but you take OEMXIPKernel and OEMDrivers from a T-Mo rom and install them instead of the WWE ones?

yosi199 said:
Basically, you work on a WWE rom as the base but you take OEMXIPKernel and OEMDrivers from a T-Mo rom and install them instead of the WWE ones?
Click to expand...
Click to collapse
The wording here can be a bit confusing - TMOUS ROMs are WWE anyway (2.13 being the last) but the latest 1024mb ROM is 2.14, which is CHS language.
You could use any base you like and just include the OEMXIP and OEMDrivers from a 2.1x ROM to make it fully compatible. I use a WWE 1.72 base (because I find it the most stable) and the OEMDrivers and OEMXIP from 2.14 (because it's the latest available). I then had to replace several bluetooth dll's and mui's in the OEMDrivers as they are in CHS and I want WWE - I just copied them over from the 1.72 WWE OEMDrivers package. If you used the 2.13 OEMDrivers they would already be WWE...
I also have the 2.10 touch.dll and touchgl.dll files copied to my OEMDrivers as these have better touch response.
The easiest way would be to just use the 2.13 base (it's 1024mb HD2 compatible and it's already WWE) and use x.xx.50.x series radios...