[KITCHEN][7/Oct/09]ELF(in) Kitchen(s)[ONLINE]

[kokotas]

New - Simple To Use - Light - Kitchen based on bepe's PRB 2.1 : B2_Kitchen (http://rapidshare.com/files/289949293/B2_Kitchen_1_0_4.7z)
Try it, change it if you know what you're doing, play with it and have fun!

Basic Usage:
0.Open with any text editor the two batch-files inside the kitchen in order to read them. Yes!There are some helpful comments inside them. Also read any *.ReadMe.txt for additional help.
1.Place any ROM you want to dump inside BaseROM (folder) and run the dump_rom.bat
You'll get the full dump of the ROM - XIP & Imgfs (sorted!).
From XIP, you will only need MSXIPKernel (folder)! KEEP the provided Elfin (folder) intact !!
2.Do your cooking stuff...WITHOUT changing the kitchen's structure(compatible with the new builds-Packages floating around)!
Meaning that you place your files like this:
OEM/
--------%locale%/OEM_Lang_%locale%
--------COMMON
--------dpi_96/OEM_DPI_96
ROM/
--------%build%/MSXIPKernel
--------Elfin
SYS/
--------%build%/
-----------------dpi_96/
------------------------%locale%
------------------------COMMON
-----------------dpi_96_resh_240_resv_320/
-------------------------------------------%locale%
-------------------------------------------COMMON
-----------------SHARED/
-------------------------%locale%
-------------------------COMMON

**DO NOT CHANGE the ROM/Elfin!!!
3.Edit according your needs\taste the "UserConfig.ini".
REM ---User_Configuration---

::PRBSettings
set LOCALE=0409
set BUILD=19972

::PagepoolSetting
set PagePoolSize=12

::CompressionSetting(XPR_or_LZX)
set COMPRESSION=XPR

::YangSettings
set ModelID=ELF0*****
set CID=11111111
set Ver=3.14.706.02
set Lang=WWE
4.Run build_rom.bat to create the final flashable ROM file(*.nbh) inside RELEASE (folder).
5.Before you flash it , you could still change the pagepool size by using the PagePoolChanger inside TOOLS (folder).
**Microsoft Visual C++ 2008 Redistributable Package (http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&DisplayLang=en) is required!
Happy Cooking;-)

[kokotas]

INTRO:

I started trying to make a kitchen for our phones based on bepe's Extended Kitchen (http://forum.xda-developers.com/showthread.php?t=365664) and this is the FINAL thing(Check ChangeLog).
Basically, I re-organized the stuff in my pc in a way to function through ONE main DOS-window. So I don't actually feel that I made anything new...
I take no credit!

************************************************** ************************************************** ****************
CREDITS TO:

bepe for the kitchen and XIPPort tools,
pof for the USPL, cmonex for the HSPL
itsme & tadzio for the brilliant but simple tools,
ervius for the PackageTool&BuildOS ALLinONE,
Noonski for the cooking class [This is how newbies gain the knowledge to cook]
Ababrekar for guideness in porting OS from another device
htctouchp for sharing his knowledge&helping me make any fixes&upgrades
and many more members/developers of this forum which I consider as a free on line school!

************************************************** ************************************************** ****************
ELF(in) Hybrid Kitchen (http://i279.photobucket.com/albums/kk145/k0k0tas/Kitchenv3.jpg)

INSTALLATION:

1. Install on your pc Microsoft Visual C++ 2008 Redistributable Package (http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&DisplayLang=en) and Microsoft .NET Framework 3.5 (http://www.microsoft.com/downloads/details.aspx?FamilyId=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en)!
2. Remove any previous version(if any)of the kitchen(shortcuts too) before "installing" the newer!
3. The archive should be extracted directly to the Drive where Windows are installed (most cases C:\) , otherwise nothing will work!
4. Once you do that, go into C:\ELF(in)_Hybrid_Kitchen and double-click "First_Run_For_ELF(in)_Hybrid_Kitchen.bat"!
5. IF you're using Windows Vista, make sure USER ACCESS CONTROL is turned OFF!

Direct Download through: Rapidshare (http://rapidshare.com/files/281779087/ELF_in__Hybrid_Kitchen_v2.0.8.exe)

************************************************** ************************************************** ****************
DESCRIPTION:
(Be patient and keep your eyes on the DOS window for additional help&instructions while using this kitchen)

Main Functions:
[a] Dump any ROM from Kaiser, Polaris, Diamond, Xperia, Raphael, Elf(in)...
You may use these formats:
****.nbh (eg: RUU_Signed.nbh, Blue_Elves.nbh, etc) ,
****OS.nb (eg: New-OS.nb, 19588-OS.nb, etc) or ***windows.nb (eg:Mobile_windows.nb, New_windows.nb, etc) ,
****imgfs.bin (eg: imgfs.bin, new_imgfs.bin, etc) .
****.payload (eg: OS.nb.payload, 20270_OS.nb.payload, etc) . <- NOT FOR ELF(in) !
****.raw(only Part01.raw & Part02.raw) .
You get new OEM, SYS and xip.bin(unless you used *imgfs.bin) into C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\Temp .
If you used an ELF(in) ROM then you'll get a full dump, OEM, SYS and XIP, that you could move to C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX\ and use it as a cooking base .
Port any XIP from Kaiser, Polaris, Diamond, Xperia... You need xip.bin .
It requires:
NOT to change Ref_XIP folder inside C:\ELF(in)_Hybrid_Kitchen\Prepare_XIP and
If you have any problems in XIP Porting you have all the needed tools inside C:\ELF(in)_Hybrid_Kitchen\Prepare_XIP to try manually port the xip (http://forum.xda-developers.com/showthread.php?t=438676) .
[c] Build your OS.nb (using the Ervius PkgToolsBuildos which can autofix & autorelocate SYS) .
You'll get the option to make a dumpable ROM using PkgToolsBuildos (by keeping unticked the box next to "All packages in one:") .
NOTE1: Inside ..\Build_ROM the OEM , SYS and ROM\XIP folders are empty . You may "fill" them with the required files .
NOTE2: Because Ervius PkgToolsBuildos is included in the kitchen, you could always use the functions that it provides apart from those described here .
NOTE3: If your xip_out.bin or out.bin is smaller than 2,49MB you could use the attached os.nb.payload (http://forum.xda-developers.com/attachment.php?attachmentid=228357&d=1253098153) (where imgfs start @ 0x280000)
[d] Flash any ROM to your device .
If you have a CID Locked device you have the option to flash a ROM using SoftSPL & your device remains CID Locked with the same SPL !

Additional Functions:
[1] Convert any cab to an OEM Package using Ervius Package Creator .
[2] Create a cab using IABovine's QuickCab 2.0 .
[3] Convert a bitmap to a Splash.nb (& reverse) using pof's nbimg .
[4] Convert files to modules & reverse using RecMod and reversmode . Not all files can be converted to modules.
[5] Convert 24 bit .bmp to .brn and reverse (for editing Cube gfx) .
[6] Compress executable files using UPX 3.03 .

Panel:
Easy access for many tools .

This is free to use or edit but [B]at your own risk, I take no responsibility for any damage caused to your phone!

[kokotas]

A) Basic Usage
1. Lets say you want to use a SHIPPED or DUMPED (NOT a COOKED!) ELF(IN) ROM as a Base.
--1.1.Double click the desktop-shortcut "Main Menu"
--1.2.Press [a]
--1.3.A window pops up beside the DOS screen. Place in there the RUU_Signed.nbh and close the window!
--1.4.Press [1]
--1.5.When the process is completed (& pressing any key returns you to main menu), you get another window opened with the files you want:
Packages(OEM&SYS)
XIP(folder)
xip.bin
--1.6.Keep that window open and double click the desktop-shortcut "Kitchen"
--1.7.Copy OEM and SYS to C:\ELF(in)_Hybrid_Kitchen\Build_ROM\
--1.8.Copy the XIP(folder) to C:\ELF(in)_Hybrid_Kitchen\Build_ROM\ROM\

2. The Base for cooking your ROM is set! Either clean up the OEM folder from things you wish to be removed or just (re)build the ROM.
--2.1.Double click the desktop-shortcut "Main Menu" (if you closed the main menu window)
--2.2.Press [c]
--2.3.PkgToolsBuildos starts
--2.4.Go to BuildOS Tab and click Load Rom.Select which Packages to include and press the green play button[Go]
--2.5.When this process is completed you'll have your OS.nb inside the "temp" folder and the (final product) RUU_Signed.nbh is generated in two places,
(i)..\CustomRUU\ <= For flashing CID Unlocked phones
&
(ii)..\RUU\ <= For flashing CID Locked phones using SoftSPL

! => ayyu3m's great [PICTORIAL] COOKING YOUR 6.1 ROMS USING ELF(in) HYBRID KITCHEN (http://forum.xda-developers.com/showthread.php?t=564261)

B) Ref_XIP folder inside Prepare_XIP is the latest 3.10ROM's XIP, but modified as follows:
-removed modules:
cachefilt.dll, hd.dll, mencfilt.dll, osaxst0.dll
-removed files:
boot_ms.rgu, bmui.nb0
-edited files:
boot.hv, boot.rgu,
REMOVED ENTRIES:
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\Fil ters\CacheFilt]
"Dll"="CacheFilt.dll"
"Order"=dword:2

[-HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\Fil ters\CacheFilt]
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Index"=dword:00000001
"Prefix"="DRM"
"Dll"="lsomacore.dll"
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\L sFilter]
"Order"=dword:00000001
"Dll"="LSFILTER.dll"
[HKEY_LOCAL_MACHINE\Init]
"Launch98"="TimeWizard.exe"
-edited modules:
nk.exe
RTC is enabled
-ALL MSXIPKernel modules are relocated to achieve better XIPPorting

**If you include LockStreamDRM PACKAGE in your ROM and you use the Ref_XIP as your \ROM\XIP(folder), ADD the removed (from boot.rgu) entries
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Index"=dword:00000001
"Prefix"="DRM"
"Dll"="lsomacore.dll"
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\L sFilter]
"Order"=dword:00000001
"Dll"="LSFILTER.dll"
[HKEY_LOCAL_MACHINE\Init]
"Launch98"="TimeWizard.exe"
in the PACKAGE's *.rgu.

C) Building your ROM
When you are building your ROM you need:
ROM\XIP(ALL FILES and MODULES) ,
ROM\romhdr.bin and
ROM\OS.nb.payload
This option builds the out.bin(buildxip.exe is used)from the XIP(folder).

D) PP Patching is included in the kitchen operation!
You just set your favorite pp size at the beginning(installing) and each Rom you build is already patched!
If you make the following hex change in nk.exe's S000
i've another method for u guys to change the PP. search the 03 15 A0 03 02 15 A0 13 00 10 83 E5 62 C2 FF EB in yours S000 of nk.exe and change the string marked in Red color to 00 00 A0 E1. from there onwards u can simply use the old Multi-platform PP changer.exe (that is also found in kaiser kitchen) to change ur PP on the OS.nb. this should make the kitchen even simpler
PS: this method works regardless of the device
then the kitchen's PP Patching doesn't work!
You should use the suggested by Aman Multi-platform PP changer v2.21 which is included in the kitchen's panel!
NOTE: I don't have an ELF to test, but after the above change then I think that the pp size is the same for both ELF&ELFIN(not dynamic).

[kokotas]

CHANGE LOG:

V2.0.8
1.WMReloc added in tools to support WM 6.5

V2.0.7
1.One way to port xip - one way to build rom
2.Updated (Ervius)PkgToolsBuildos to version 5.3

V2.0.6
1.Updated QuickCab to latest version

V2.0.5
1.Updated HTCRomImageEditor to latest version
2.Fixed an error regarding option 1 in XIP-Porting - XIP from a device that doesn't have all the MSXIPKernel modules could create problems (i.e. XIP from NIKI doens't have initvmmap.exe, so it is required to use the initvmmap.exe from our device's xip)

V2.0.4
1.XIP Porting is changed.There are still 2 options with the same result, but option 1 is now based on "sp3dev's way" (http://forum.xda-developers.com/showpost.php?p=2428300&postcount=39) with the usage of evalu8t0r's useful tool (http://forum.xda-developers.com/showpost.php?p=3038347&postcount=84)

V2.0.3
1.Minor Fix (a wrong shortcut in the Panel)
2.Updated os.nb.payload (Only change is less size ~3MB) to make the whole kitchen smaller

V2.0.2
1.Minor Edit regarding CustomRUU & RUU (folders) to avoid confusion.

V2.0.1
1.Added CFFExplorer
2.Removed ResHacker
3.Added ThemeGenCE
4.Added file unsigner

V2.0.0
1.Added cmonex' autopatcher
2.Added TinyHexer
3.Changed the kitchen structure
4.Changed the Main menu functions
5.Added "Panel" for accessing most of the tools
6.Added QuickCab

V1.4.3
1.New OS.nb.payload(taken from 3.10Rom) without ULDR , reduced space between XIP & IMGFS(xip start @ 0x400 and imgfs start @ 0x300000 so there is enough space to even use original xip.bin), and less size(~28MB) to reduce download size
2.Ref_XIP_OUT & Ref_XIP folders inside Prepare_XIP include OEMXIPKERNEL from 3.10Rom
3.Added DSMInfo tool
4.Removed option regarding hex editing the ROM
5.Added MP PagePool Changer v2.21
6.README (http://forum.xda-developers.com/showpost.php?p=2939708&postcount=212)

V1.4.2
1.Only one part
2.Removed Extra Options (w, x, y, z)
3.New OS.nb.payload(taken from 3.07Rom) without ULDR and less size(~29MB) to reduce download size
4.New XIP Porting option(1) to build xip_out.bin in order to use it in...
5.New building option(1)
6.New CustomRUU for flashing CID Unlocked phones
7.Added a command line icon extractor(DragN'Drop style)
8.Modified the offsets for pp_patching (to 0x045210) in order to use OEMXIPKernel from 3.07ROM only
9.Added SYSVersion application to see what version is the (SYS)ROM you're dumping
10.Collected&added some tools that you might need(eg. XIPTools, XipModuleInfo, htcRIE_0.4.0.47, etc)
11.Ref_XIP_OUT & Ref_XIP folders inside Prepare_XIP are the latest 3.07ROM's XIP, but modified as follows:
-removed modules: cachefilt.dll, hd.dll, mencfilt.dll, osaxst0.dll
-removed files: boot_ms.rgu, bmui.nb0
-edited files: boot.hv, boot.rgu, 723fb954-d931-4348-b672-82a188e587b5.rgu
-ALL MSXIPKernel modules are relocated to achieve better XIPPorting

---------------------------------------------------------------------------------------------------------------------------------------------------------
V1.4.1
1.Added pp_patching (for 2.2x based ROMs=OEMXIPKERNEL from 2.2x ROM) at the end of the OS-building(You get the chance to configure it yourself. If you don't change it then the pagepool will be at default size-12MB for ELFIN&8MB for ELF-)
2.The *.nbh will be auto-generated at the end. If the size is less than 50MB it will be moved to C:\ELF(in)_Hybrid_Kitchen\Flash_ROM\ROM_for_SDCard _Flashing and renamed to ELF0IMG.nbh(You get the chance to configure the htc rom tool's info yourself)
3.First_Run_For_ELF(in)_Hybrid_Kitchen.bat gives you the chance to make some personal settings! Don't forget to run it!

V1.3.4
1.Minor changes
2.Reconstructing *.raw files added

V1.3.3
1.No OS.nb.payload - Could be downloaded separately - Reduced size!
2.Added Opal rom dumping
3.Some lite-changes in the batches
4.XIP porting in 2 ways(1less)

V1.3.2
1.Fixed the problem when dumping ELF(in)'s ROM
2.Removed option to create PPC applications

V1.3.1
1.Fixed SplashScreen-converting bug
2.Added XIP from OS 5.2.20721

V1.3
1.Added patched SPLs 1.17.0000 , 1.19.0000 & 2.28.0000 for USPL
2.Added option to optimize files(UPX3.03)
3.New way to convert .nb<->.bmp(pof's nbimg)
4.Added "ability" to dump *.payload

V1.2
1.Added option to create PPC applications
2.Added option to create SDConfig.txt for UC Roms
3.Added 2.26.0000 patched SPL for USPL
4.Removed OEM&SYS files from ELFIN_DEV_v2.1_Build_19XXX
5.Updated HTCRT v. 1.1.1.0
6.Fixed the "no files - only modules" when dumping a rom

V1.1
1.Added option to sign files
2.Fixed some lines in batch-files
3.Every feature is tested

[Piranha1]

Nice job Kokotas.

[!Aman!]

great job bro :)
i would like to test ur kitchen.

[kokotas]

Nice job Kokotas.
great job bro :)
i would like to test ur kitchen.

Thanks guys, but it will be great only if it works for everybody!
htctouchp I'll pm you the password for the download link.
Regards!

[!Aman!]

Thanks man, but it will be great only if it works for everybody!
I'll pm you the password for the download link.
Regards!
TOGETHER we all can MAKE SURE that it works for everybody ;)

[melih43]

how can I obtain pass? I will translate ebglish rom to Turkish and I need that tool..

[Noonski]

Nice work.

Not going to switch right away at the moment.

But this looks very good.

[gullum]

I'm on the lookout for a cheep Touch so this will come in handy if I get my hands on a touch....

[melih43]

I'm on the lookout for a cheep Touch so this will come in handy if I get my hands on a touch....

gullum I have touch and I can't wait to cook a new room for touch

[optima]

ill have a go i got a rom on my phone that that is needed in the upgrade rom list but i have been able to remove it

[eremite]

i need to lock down some features of my works PDAs and would love to try your kitchen to attempt this.

can i have a password?

[gullum]

Got a Touch tonight for under 200$ used of cause :D so now I want a kitchen to make roms :D

[CyZeeK]

Sit taken:)

Well deserved!

Gr8 job, Ill keep an eye.

[sangsiam]

This is fantastic and I'd like to try it. I'd like to cook my rom using this kitchen. Would you pls. give me a password.

[kokotas]

Removed password protection!The download link is open for everyone!
Read 1st post before starting to play with it!Get used to it and read carefully!
Some features are NOT tested yet!
Hope to hear some good news!
Even better...hope to hear that someone makes it better!
I'm done!Back to my readings and to Solid State Physics(I hate that lesson:))
Best Regards!

[gullum]

This is on it's way to my pc now :D thanks in advance
I've already changed Bepe's kitchen to fit my cooking but this one seams more advanced so thanks again

[!Aman!]

Removed password protection!The download link is open for everyone!
Read 1st post before starting to play with it!Get used to it and read carefully!
Some features are NOT tested yet!
Hope to hear some good news!
Even better...hope to hear that someone makes it better!
I'm done!Back to my readings and to Solid State Physics(I hate that lesson:))
Best Regards!
u need to modify the Create_ROM_for_ELF.bat file used for Ervius' buildOS tool. its not working right now, pls check it :)

[absorber786]

Mirror please?? (mediafire possibly)

thanks in advance
:D

[kokotas]

u need to modify the Create_ROM_for_ELF.bat file used for Ervius' buildOS tool. its not working right now, pls check it :)
I left inside the bat that I was experimenting with!Sorry!:o
cd ROM


..\TOOLS\buildxip.exe <====== Don't use -b parameter, it crashes

if not "%errorlevel%"=="0" goto error
Attaching bellow the right bat.I will upload again the 1st part with the correct Create_ROM_for_ELF.bat.
Regards!

-edit:It seems that I can't get the stupid zip attached!Is it my connection or the server?Who knows?Just edit the bat file as above to make it work!

[!Aman!]

I left inside the bat that I was experimenting with!Sorry!:o
cd ROM


..\TOOLS\buildxip.exe <====== Don't use -b parameter, it crashes

if not "%errorlevel%"=="0" goto error
Attaching bellow the right bat.I will upload again the 1st part with the correct Create_ROM_for_ELF.bat.
Regards!

-edit:It seems that I can't get the stupid zip attached!Is it my connection or the server?Who knows?Just edit the bat file as above to make it work!
no, this is not enough ... also have to remove the following part:

attrib boot.rgu -r -s -h -a
del boot.hv
del boot.rgu


either u can remove it, or put REM in front of all commands. then everything should work :)

[kokotas]

Thanks to htctouchp I corrected that bat file and everything should work now!I updated the file in rapidshare folder too!
For those who downloaded the kitchen before this fixing, just go inside C:\ELF(in)_Hybrid_Kitchen_V1\ELFIN_DEV_v2.1_Build_ 19XXX\TOOLS and edit the "CREATE_ROM_For_ELF.bat" as described in the above post!
Regards!

[!Aman!]

also, i think u can remove the elf.nb and elfin.nb files from valid_nb folder in _ROM and provide them as a separate links so that ppl can download them according to elf/elfin. this will reduce the size of the kitchen :D

[Ameet]

hey sweet work koko.. not going to use right now but will surely switch over soon :D tried combining ivanmmj's porting kitchen (http://forum.xda-developers.com/showthread.php?t=391524) with your kitchen to make it portable and cookable for elfins? ;)

[!Aman!]

hey sweet work koko.. not going to use right now but will surely switch over soon :D tried combining ivanmmj's porting kitchen (http://forum.xda-developers.com/showthread.php?t=391524) with your kitchen to make it portable and cookable for elfins? ;)
u can switch right away :D..i did already ;)
plus i dont think we need ivan's porting kitchen (although that's good one too)

[Ameet]

u can switch right away :D..i did already ;)
plus i dont think we need ivan's porting kitchen (although that's good one too)

sweet!! i'll switch right away.. :D

i suggested ivan's kitchen coz its easier to port from there ;)

[!Aman!]

porting in this kitchen is ALSO easy. plus u get 3 options of XIP porting, u can chose anyone of ur liking.

[Ameet]

As you will see, it's a little monster :)

hey koko.. is the size so huge coz u included the nb file from bepe's kitchen too? is it possible for u to post a only-tools version of ur kitchen? dont wanna waste time downloading the whole monster our which the files re already with me ;)

[Swiftblade]

hi koko bro... great works you done there! I have doing those stuff manually all these while and now everything is in one kitchen... ;)

I'm downloading as I speak and will use it to dump the Diamond new ROM 19591. Well Done!

[kokotas]

hey koko.. is the size so huge coz u included the nb file from bepe's kitchen too? is it possible for u to post a only-tools version of ur kitchen? dont wanna waste time downloading the whole monster our which the files re already with me ;)
Hey Ameet!I'll be waiting any observations bro!Give it a try!
The size of the 1st part is so big because I included OS.nb.payload in \ROM folder and I left some files in \SYS as a template for cooking!
For the 2nd part of the kitchen I included 2 extracted .NB files:
One is the ELF-template from this official rom:RUU_Elf_HTC_WWE_1.11.405.1B_4.1.13.42_02.93.90 _Shi p.exe (http://rapidshare.com/files/117029689/RUU_Elf_HTC_WWE_1.11.405.1B_4.1.13.42_02.93.90_Shi p.exe)
The other is the ELFIN-template from this official rom:RUU_Elfin_DOPODASIA_WWE_2.20.707.1B_4.1.13.51_ 03.0 7.90_BLUE_Ship_Reduced.exe (http://rapidshare.com/files/113557640/RUU_Elfin_DOPODASIA_WWE_2.20.707.1B_4.1.13.51_03.0 7.90_BLUE_Ship_Reduced.exe)

hi koko bro... great works you done there! I have doing those stuff manually all these while and now everything is in one kitchen... ;)

I'm downloading as I speak and will use it to dump the Diamond new ROM 19591. Well Done!
Thanks Swiftblade!Hope you find it useful!
I see that you've got your Diamond!;)That means that you will stop making ELF ROMs?!?Please don't stop cooking for us!:)

Best Regards!

[Swiftblade]

Thanks Swiftblade!Hope you find it useful!
I see that you've got your Diamond!;)That means that you will stop making ELF ROMs?!?Please don't stop cooking for us!:)

Best Regards!

Hi koko... actually I love to cook roms for the Elf and Elfin because the enhancements and improvements make to this little fella is so significant and appreciated. In the case of the Diamond, you can say almost everythings are already in it and appears that the only improvements is possibly its speed and make it trimmer.

Unfortunately, I now have limited access to my now Elfin for testing the roms as it is literary in the possession of my dear ones. I have to kinda "plead" with her to allow me to use it... haha:)

[Ameet]

Hey Ameet!I'll be waiting any observations bro!Give it a try!

hey koko.. will surely download and report this amazing kitchen :) looks good but too lazy to download the whole monster.. can u please pm me the only-tools version? please? :D i already have the .nb templates so dont need them to download again

awaiting my new comp tonight hopefully.. so should be back to cooking then :D

[!Aman!]

hey koko.. will surely download and report this amazing kitchen :) looks good but too lazy to download the whole monster.. can u please pm me the only-tools version? please? :D i already have the .nb templates so dont need them to download again

awaiting my new comp tonight hopefully.. so should be back to cooking then :D
i'll mail u the tools without *.nb, payload, OEM, and SYS...just wait for half an hour :D

[Ameet]

i'll mail u the tools without *.nb, payload, OEM, and SYS...just wait for half an hour :D

okie dokie.. wish u could also mail me my comp ;)

[!Aman!]

okie dokie.. wish u could also mail me my comp ;)
LOL, are manager sahab!!! aapko computers ki kami ho sakti hai bhala :D???

[Ameet]

LOL, are manager sahab!!! aapko computers ki kami ho sakti hai bhala :D???

:D no computer shortfalls.. :D had sent my comp for a major upgrade.. will be able to cook 5 roms at a time wen i get it back ;)

[!Aman!]

:D no computer shortfalls.. :D had sent my comp for a major upgrade.. will be able to cook 5 roms at a time wen i get it back ;)
thats great!!! whats that major upgrade supposed to be? btw, did u get the kitchen files?

[Warz_NL]

Thanks for the kitchen.

I am going to try it out right now :)

Hopefully I wont kill me device again :p

[Ameet]

thats great!!! whats that major upgrade supposed to be? btw, did u get the kitchen files?

hey thnx for the files.. upgrading to a nice 500gb hdd and dual graphic cards with a cool 16gb ram.. can run 5 kitchen at a time :D

[!Aman!]

hey thnx for the files.. upgrading to a nice 500gb hdd and dual graphic cards with a cool 16gb ram.. can run 5 kitchen at a time

:eek::eek::eek:
did u start cooking again or still waiting for ur pc (or super computer :p)?

[Ameet]

:eek::eek:
did u start cooking again or still waiting for ur pc (or super computer :p)?

nah... just got a call, getting the pc tomorrow :(

[Ameet]

hey koko. i download ur kitchen but m in serious need of a readme guide on how to use it :( its a great complex kitchen with everything useful :) wanna use it.. can u post a how-to-use or something?

[kokotas]

hey koko. i download ur kitchen but m in serious need of a readme guide on how to use it :( its a great complex kitchen with everything useful :) wanna use it.. can u post a how-to-use or something?
Hi Ameet!
1st Post has some useful info about this kitchen and how to use it(under DESCRIPTION),
plus I have all the instructions needed showing up during each process.
ALWAYS have your eyes on the DOS window;)
When I'm done with my exams I'll have the time to make a more detailed "How_To" if it is still needed by the majority of this kitchen's users.
Happy Cooking with your New SPC[=SuperPC:D]
Regards!

[Ameet]

Hi Ameet!
1st Post has some useful info about this kitchen and how to use it(under DESCRIPTION),
plus I have all the instructions needed showing up during each process.
ALWAYS have your eyes on the DOS window;)
When I'm done with my exams I'll have the time to make a more detailed "How_To" if it is still needed by the majority of this kitchen's users.
Happy Cooking with your New SPC[=SuperPC:D]
Regards!

ah!! i overlooked the first post :)

SPC gives me a new idea for a new rom ;)

[!Aman!]

hey koko. i download ur kitchen but m in serious need of a readme guide on how to use it :( its a great complex kitchen with everything useful :) wanna use it.. can u post a how-to-use or something?
if u need help with anything, i can help also coz i was the first one to test his kitchen and i'm kind of familiar with batch files used by this wonderful kitchen

[Noonski]

Hey i got's a copyright on SPC.

But i'm giving you a license to use it for free ;)

[kokotas]

Updated 1st post with new version.
If you give it a try, please feedback!

[!Aman!]

good work koko, downloading the new version now. i'll give my feedbacks later ;)

[kokotas]

1.Why don't I get 3 options for XIP Porting?
Attaching the batch file for XIP Porting for those 10 people who d/l the 1st Part till now. Just overwrite the old one in C:\ELF(in)_Hybrid_Kitchen\Batch with the attached one. Sorry for the trouble:o! I just left the old batch file inside the folder I zipped and that is why you probably don't see 3 options for XIP Porting:)

2.Why when I try to build my Os.nb with Ervius PkgToolsBuildos the process stops?
Also attaching the batch file for Creating Elf Os.nb. Overwrite the old one in C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX\TOOLS with the attached one or edit the batch file yourself.

3.Why do I get only modules when dumping a rom?Where are the needed files?
Browse to C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\Tools and delete these two files
ImgfsFromNb.sln
ImgfsFromNb.suo
in order to get modules and files when dumping a rom.

4.Why can't I find my CID & DID?
Browse to C:\ELF(in)_Hybrid_Kitchen\Batch and edit the FindCID_DID.bat!
There is a mistake in one line :
"...ELF(in)_Hybrid_Kitchen_V1\Batch"
Make it :
"...ELF(in)_Hybrid_Kitchen\Batch"

The big archives in Rapidshare are also updated with the corrected (above) files!

5.Is it possible to be able to dump *.payload files too?
Yes! Download the attached DumpNBH.zip and extract to C:\ELF(in)_Hybrid_Kitchen\Batch overwriting the old one. You should be able now to dump *.payload files too!

6.Why the generated SplashScreen from this kitchen is not working right?
There is a parameter missing in the commands, so download the attached fixed Splash.bat and overwrite the old one in C:\ELF(in)_Hybrid_Kitchen\Batch!

7.Want to try something new?
You need to have perl installed(ActivePerl is free)!
You might want to add some packages: "XML::Registry and XML::Parser" .
Then download the KitchenUpdate.zip and extract directly to your c: drive overwriting old files(BUT FIRST backup the batch folder). You'll add in this way option to convert *.xml to *.reg & reverse!
I have seen that it works with most(NOT ALL)the files I tried! So try it and feedback!

Regards!

[!Aman!]

Attaching the batch file for XIP Porting for those 10 people who d/l the 1st Part till now. Just overwrite the old one in C:\ELF(in)_Hybrid_Kitchen\Batch with the attached one. Sorry for the trouble:o! I just left the old batch file inside the folder I zipped and that is why you probably don't see 3 options for XIP Porting:)
The big files in Rapidshare are also updated with the correct bat!
Regards!
hey koko...i think it would be better if u dont include the NBs and payload in the kitchen. give a separate link for them so that the kitchen's size is as much less as possible. downloading abt 200 mb is too much for ppl with slow internet.

[kokotas]

You've told me before the same thing!
So I listened to you(and Ameet's request also):) and
I have already made available an
OnlyTools version of ELF(in)_Hybrid_Kitchen_V1.2_(Pt.1) (NO OEM,SYS,os.nb.payload)
in 1st Post under SEPARATED TOOLS and it's only 25MB ;)
-edit:
I am thinking about doing the same thing for part 2(those nbs needed for DumpingROM could be placed in another part) as you suggested.
Regards!

[!Aman!]

You've told me before the same thing!
So I listened to you(and Ameet's request also):) and
I have already made available an

in 1st Post under SEPARATED TOOLS and it's only 25MB ;)
oops, i overlooked it :D

[kokotas]

I did a minor update (so no need to call it another version).
I updated htcrt to newer version 1.1.1.0 and
I updated the XIP folders with newer from Diamond's OS 19591;)
Remember, that a lighter version (only with the tools) is available too
to reduce size.
Check 1st post!

Regards!

[voided]

Hi Pple,

I have tried to to flash the ROM cooked from this kitchen(without any modification) directly on my HTC Elf(126mb/64mb) and found that none of the HTC OEM app under my settings works.

When I double click the "Backlight", "Power", "Clear Storage", "Device Information", etc.. icons under my settings nothing happen. No error message at all. But if i use a the fexplorer to launch the exe from "\Windows" It is able to launch.

Any kind soul here have solution have a solution to this problem?

I have compared the "mxip_oem_translation_0409.provxml" file with the shipped rom for my device.. eveything seems fine... Thanks in advance.

[!Aman!]

Hi Pple,

I have tried to to flash the ROM cooked from this kitchen(without any modification) directly on my HTC Elf(126mb/64mb) and found that none of the HTC OEM app under my settings works.

When I double click the "Backlight", "Power", "Clear Storage", "Device Information", etc.. icons under my settings nothing happen. No error message at all. But if i use a the fexplorer to launch the exe from "\Windows" It is able to launch.

Any kind soul here have solution have a solution to this problem?

I have compared the "mxip_oem_translation_0409.provxml" file with the shipped rom for my device.. eveything seems fine... Thanks in advance.
u can not use mxip_oem_translation_0409.provxml and htccpl with diamond builds. read the thread related to surface ROM, Ameet has explained the procedure over there. this is not a problem with the kitchen:)

[voided]

u can not use mxip_oem_translation_0409.provxml and htccpl with diamond builds. read the thread related to surface ROM, Ameet has explained the procedure over there. this is not a problem with the kitchen:)

Hi htctouch,

Are you able to point me the the post? The closest I can find is this one: http://forum.xda-developers.com/showthread.php?p=2275246&highlight=settings#post2275246 But it doesn't say anything much... Thanks

[!Aman!]

Hi htctouch,

Are you able to point me the the post? The closest I can find is this one: http://forum.xda-developers.com/showthread.php?p=2275246&highlight=settings#post2275246 But it doesn't say anything much... Thanks
check this out:
http://forum.xda-developers.com/showpost.php?p=2356597&postcount=326

[voided]

Maybe I'm stupig but I don't understand the guide... especially the part about MyCPL.cpl.. Where did he get this file...

[!Aman!]

u get this in OEMDrivers folder after dumping the diamond ROM. anyway, i'll attach it here to make it easy for u. any other difficulties?

[winderp]

Thanks bro, it's great !

[Noonski]

Doing A great Job and it's looking Solid.

Hope making this thread Sticky gets you the attention to make it better.

Cheerz

[voided]

u get this in OEMDrivers folder after dumping the diamond ROM. anyway, i'll attach it here to make it easy for u. any other difficulties?

Sorry didn't have change to try it till now. Thanks you are the man. It worked like a charm:)

[!Aman!]

6.Fixed the "no files - only modules" when dumping a rom

how did u fix it brother?

[Ameet]

how did u fix it brother?
What does it do? and What is the benefit of having "only modules" in the ROM?

[!Aman!]

What does it do? and What is the benefit of having "only modules" in the ROM?
it doesnt affect anything even if u dont have the files inside the module folders. but having files inside module folders is benificial if u just want to have a look what's inside e.g. i use resource hacker on most the files to see whats inside them and if there are only modules, first i've to convert them into files which costs me a few precous minutes:D

[kokotas]

Hey guys!
What does it do? and What is the benefit of having "only modules" in the ROM?
The benefit is that you may reduce the size of the rom. I'm sure you'll find it useful!;)
But...
it doesnt affect anything even if u dont have the files inside the module folders.
Actually I think that NOT all files could be converted to modules, as far as I have tested till now! Could anybody help and check that?
Cook a ROM only with modules and see if you're missing anything when it boots...
Regards!

[Ameet]

Actually I think that NOT all files could be converted to modules, as far as I have tested till now! Could anybody help and check that?
Cook a ROM only with modules and see if you're missing anything when it boots...
Regards!

You are right. Most of the .exe files can't run after being converted to modules like Camera, Backlight and so on. But it does save a lot of real estate when the convertable files are modules :)

[!Aman!]

Hey guys!

The benefit is that you may reduce the size of the rom. I'm sure you'll find it useful!;)
But...

Actually I think that NOT all files could be converted to modules, as far as I have tested till now! Could anybody help and check that?
Cook a ROM only with modules and see if you're missing anything when it boots...
Regards!
actually what i mean to say is, that u can just start using the dumped SYS, OEM etc without having to bother about modules/files. if something is not converted automatically into a module by the kitchen, let it be like that. i personally dont try to convert any dll or exe into a module. in first version of kitchen, it only generated the modules of the files which could be converted into modules while other kitchen produced both the dll and its module. this was the only observation i had.

[VJstar]

I came late, and good slow to download. But thank you very much for the work has brought us such a powerful tool:D

[911sniper]

Good work! Thanks!

[Noonski]

Same opinion on the Modules.

I was looking for an easy way to convert files into them.

But it's always best to do it step by step flash test.

Same goes for compressing files in rom with UPX, weird stuff can start happening.

But in some cases the size and speed you get back do make a difference.

It's an advanced kitchen so good to have it around.

[kokotas]

Same opinion on the Modules.

I was looking for an easy way to convert files into them.

But it's always best to do it step by step flash test.

Same goes for compressing files in rom with UPX, weird stuff can start happening.

But in some cases the size and speed you get back do make a difference.

It's an advanced kitchen so good to have it around.

Good idea man!
I'll add the upx3.03 in the kitchen!
It would be useful and fun to play with!
But I'll wait to see more confirmations for the patched 1.17SPL to include that one too and avoid uploading the kitchen twice.
Regards!

[luzbel_es]

Hello everybody! First please sorry my english :o I'm from spain.

I have a question. If i wanna get the OS 20733 from a rom of a Diamond to put into a TouchXl (Elfin) what i must to do?

If I use the [a] option (dump *.nbh) with the rom into the base folder and after I use [e] option to Flash it must work??

Thanks for all I'm very new in this!!

[Ameet]

Hey Koko. Please include Dsixda's threads in your Rollup so there wont be any need to sticky them :)

Also where are you these days? Have you checked and corrected the dead links?

[kokotas]

If i wanna get the OS 20733 from a rom of a Diamond to put into a TouchXl (Elfin) what i must to do?
This is like asking "How to port new OS & cook a ROM etc."...
A single answer is difficult!
But you may want to read some useful threads (http://forum.xda-developers.com/showpost.php?p=2443043&postcount=4) before starting all this cooking stuff!
If I use the [a] option (dump *.nbh) with the rom into the base folder and after I use [e] option to Flash it must work??
NO!
You'll see that if you follow my advice and do a little reading before cooking,
you'll answer this question easily on your own!
Hey Koko. Please include Dsixda's threads in your Rollup so there wont be any need to sticky them :)

Also where are you these days? Have you checked and corrected the dead links?
I'm here bro!Just not having anything to say nowadays!
I just saw dsixda's threads & definately including them into the sticky!
Dead links were fixed(3days ago)! Now... if you've deleted any threads in the meanwhile,
I'll check again!
Regards!

[luzbel_es]

Thanks kokotas!! I will read the threads!! Really thanks for answer!!

[Ameet]

I'm here bro!Just not having anything to say nowadays!
I just saw dsixda's threads & definately including them into the sticky!
Dead links were fixed(3days ago)! Now... if you've deleted any threads in the meanwhile,
I'll check again!
Regards!
:D Not deleted anything lately. So no worries :)

[bytespider]

Hey everyone, Im back... with new enthusiasm for my elf.
Lost interest after millions of rom flashes and never really satisfied 100%.

I've taken a look at the Diamond and looks like it has some features id like.

Anyway I've extracted the diamond rom, and i think ported the XIP...

then i try to build the ROM however it gets all the way to CREATE_ROM_ELF.bat and insert.exe crashes.

I have the redist suite installed and running bebe's kitchen unmodified works...


so i can only assume that something i did with the diamond rom isnt right.


any ideas? maybe a step-by-step? as the instructions on the porting part of the kitchen aren't as comprehensive (or existent) as the rest of the kitchen


HELP! :eek:

[kokotas]

then i try to build the ROM however it gets all the way to CREATE_ROM_ELF.bat and insert.exe crashes.

Hey!
Check #2 here (http://forum.xda-developers.com/showpost.php?p=2378379&postcount=49) and if it still crashes, tell me about it!
Regards!

[bytespider]

Hi Koko

I thought i tried that but i just tried it again and it hangs again just after the xipping section.

If im dumping diamond rom do i tell the XIP port scriot that i want and elf XIP or tell it that this was a diamond XIP?

[kokotas]

Just uploaded a fixed version with a minor update(new xip)!
It's a fix regarding SplashScreen *.nb<->*.bmp converting!
Thanks to Aman who pointed out the bug!
Actually he seems to be the only one who uses&tests this kitchen:D
and without his feedback&help, this would never get updated!
Regards!

[dsixda]

Hi guys,

Koko told me to post my problem about his kitchen, which apparently he has found as well in his own testing.

Original PM to Koko:


Hey Koko,
I'm still getting the same problem w/ Rogers Elfin and Orange Elfin ROMs with your latest kitchen. When I build, I get no Customization, all Today items are checked, and various Program shortcuts are missing.

These are the steps I did from your kitchen;
1) Chose selection "a" - dump nbh from Elfin
2) Moved OEM and SYS folder to Build directory
3) Chose "c" - build OS.nb, and used Bepe's kitchen
4) Created NBH with HTC Rom Tool, and flashed

?? Did I miss a step?



Kokotas' reply:


Well you didn't miss any step, but it seems that something is wrong with the reconstruction of the ROM in the kitchen!
Let me explain:
The thing is that I have used my own dumped ROM as a base ROM in the past without any issues!
Today I tried to make the same thing with that Orange Elfin ROM
and I got the same problems as you did!
I wondered if we are missing something from the dump(like Part01.raw(?) which I think is the XIP).
So I tried to rebuild my dumped ROM(which worked ok previously), but this time I got the same problems like those you're having!
Obviously this is a problem with the kitchen and not with the ROM nor with the way you cooked!
Please add your comments about this problem in the sticky thread so others would know that this kitchen is useless until I fix it(again)!
Thanks for the feedback!
Sorry for the trouble! You could use Hypercore for the job you want(I tested it&the generated OS is ok) until I fix this..
Best Regards!



I'm hoping for a quick fix, because this kitchen so user-friendly for me.

[Kinnara]

Hi guys,

Koko told me to post my problem about his kitchen, which apparently he has found as well in his own testing.

Original PM to Koko:




Kokotas' reply:




I'm hoping for a quick fix, because this kitchen so user-friendly for me.

I have the same problem. My base ROM is the original 2.20.707.1B Elfin ROM and my device is HTC P3452. Hope it will be fixed in the near future.

[Gartak]

First of all, thanks for the kitchen, kokotas!

However, I´m trying to use it thru trial and error, and it´s proving to be very difficulty, without any help or tutorial.

What I did so far was to extract the Touch Essentials 1.9D ROM using the kitchen. Then I removed some stuff from the OEM and SYS folders, to make it lighter.

Now I´m stuck on the "c" option: Bepe's Ext-Kitchen gives me an error (ERROR! (errorlevel: -1073740777)) and if I try Ervius PkgToolsBuildos, I have no idea on what to do, or what this tool is supposed to do!

Someone could give me some pointers? An online tutorial or something? I did lots of searching but found nothing.

Thanks in advance!

Gartak

[dsixda]

It's usually not a good idea to cook a ROM that has already been cooked, because sometimes the author has put some security feature in it, or there are some other things that may cause problems.

I would start from a regular shipped ROM and cook from there.



First of all, thanks for the kitchen, kokotas!

However, I´m trying to use it thru trial and error, and it´s proving to be very difficulty, without any help or tutorial.

What I did so far was to extract the Touch Essentials 1.9D ROM using the kitchen. Then I removed some stuff from the OEM and SYS folders, to make it lighter.

Now I´m stuck on the "c" option: Bepe's Ext-Kitchen gives me an error (ERROR! (errorlevel: -1073740777)) and if I try Ervius PkgToolsBuildos, I have no idea on what to do, or what this tool is supposed to do!

Someone could give me some pointers? An online tutorial or something? I did lots of searching but found nothing.

Thanks in advance!

Gartak

[!Aman!]

It's usually not a good idea to cook a ROM that has already been cooked, because sometimes the author has put some security feature in it, or there are some other things that may cause problems.

I would start from a regular shipped ROM and cook from there.
there is no security in that version (1.9 D) of my ROM. anyone can dump it, edit it, modify it or do whatever he/she wants.

[Gartak]

I didn´t know about the security thing, thanks for warning me!

Anyway, I chose the 1.9D because htctouchp clearly stated that this version was meant to be dumped and modified.

By the way htctouchp, that would be perfect to have this ROM with no HTC Home plugin. One of the features I´m trying to remove it exactly it.. I don´t think it fits well into a "light" ROM, but that´s just my opinion!

Thanks!

Eduardo

[!Aman!]

By the way htctouchp, that would be perfect to have this ROM with no HTC Home plugin. One of the features I´m trying to remove it exactly it.. I don´t think it fits well into a "light" ROM, but that´s just my opinion!

thats very easy. just remove the related imgaes, dlls, exe's and the rgu from OEMAPPS folder.

[dsixda]

Kokotas, do you think the problem with my cooked ROM is the OS.nb.payload file that is already there under the Build\ROM directory?

[Gartak]

Thanks again, htctouchp! I just removed all HTC Home and other stuff I didn´t want in the ROM.

After that, I copied my OEM and SYS folders from the Extract_ROM folder to the ELFIN_DEV_v2.1_Build_19XXX folder. Now it seems Ervius tool got happier, at least I could use the Load ROM button, and then the Go button. The tool started to work, but after a while, it pointed an error on CREATE_ROM_For_ELF.bat.

Please, could someone tell me if I´m in the right path? What should I do to correct the BAT error, and what´s the next step? What about the XIP thing? I don´t even know what XIP means...

Thanks a lot!

Eduardo

[Gartak]

WooHoo! Found what was wrong: I had to install VS 2008 Redist package!

That sorted everything out: I cooked my first ROM with this kitchen! Lots of things are not working well on my phone now, but it´s just a matter of fine tuning now. :)

Thanks guys!

Eduardo

[Gartak]

kokotas and htctouchp, there´s something going worng with the kitchen.

Look what I tried: I just dumped and then tried to rebuild the Touch Essentials 1.9D ROM, with no modifications at all. As htctouchp already stated, this version is intended for dumping and cooking.

I can extract everything from the ROM, no errors.

When I try the xip extraction, again, everything well. BUT, when I use the option to copy the NEW_XIP contents to ROM\XIP, it seems nothing is copied, and the default contents remain there. In other words: it seems the kitchen doesn´t use the new, dumped XIP when building the new ROM.

Since I barely know what I´m doing, I went ahead, and used ervius tool to build the new ROM (without using the XIP functions this tool offers). Corrected the size, changed pagepool size, created the NBH and flashed it.

The result? A malfunctioning ROM! I can´t active sync, can´t create GPRS or WiFi connections, can´t send SMS, several menu options do nothing, etc. In the about screen, I can see something curious: CE OS 5.2.20721 (Build 20275.1.3.3).

See? 20721 and 20275. Did I mix two ROMs of different versions? If so, I guess it´s because of the old XIP not being replaced by the new one. Does that make sense? Any pointers?

I´ll keep trying. Thanks!


Eduardo

[!Aman!]

The result? A malfunctioning ROM! I can´t active sync, can´t create GPRS or WiFi connections, can´t send SMS, several menu options do nothing, etc. In the about screen, I can see something curious: CE OS 5.2.20721 (Build 20275.1.3.3).

See? 20721 and 20275. Did I mix two ROMs of different versions? If so, I guess it´s because of the old XIP not being replaced by the new one. Does that make sense? Any pointers?

XIP was changed in the kitchen version 1.3.1, so thats normal. for other problems, u can try replacing OEM, SYS one by one. u might have missed something.

PS: if u know how to dump manually, try that. or also try dumping with hypercore.

[dsixda]

Ok, I finally got my base ROM cooked, but it was through Hypercore, as Koko suggested. It got messed up in Hybrid Kitchen due to registry issues I think. I hope you get it fixed, because it's got so much potential :)

[kokotas]

Hey guys!
I uploaded a revised version!
Please test it!

ps:If it doesn't work this time too, then I'll have to put it on hold till the end of the month cause of busy schedule.
Hope you understand...

[Gartak]

Hi Koko, I just tested it and got the same results..

Sorry if this sounds stupid, but since I´m duping a ROM (Touch Essential 1.9D), why do I need the supplied OS.nb.payload file? Isn´t the kitchen mixing up stuff from this base file to stuff from my dumped ROM?

Shouldn´t I instead find a way to extract the payload file from my dumped ROM, instead of using the supplied one?

Thanks!

Eduardo

[!Aman!]

Hi Koko, I just tested it and got the same results..

Sorry if this sounds stupid, but since I´m duping a ROM (Touch Essential 1.9D), why do I need the supplied OS.nb.payload file? Isn´t the kitchen mixing up stuff from this base file to stuff from my dumped ROM?

Shouldn´t I instead find a way to extract the payload file from my dumped ROM, instead of using the supplied one?

no, use the payload (the one inside ROM folder) which is in the kitchen.

[Gartak]

In this case, I have no clue on what may be wrong. I´ll describe in detail what I´m doing, hope someone can help me find what´s going wrong:

- After decompressing the archive and running de setup batch file, ran the shortcut in the desktop to start the kitchen.

- Chose [a] option, then copied TESS 1.9D (NBH file) to the C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\BaseROM folder, and hit option 1.

- Then I copied folders OEM and SYS from C:\ELF(in)_Hybrid_Kitchen\Extract_ROM to C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX

- Back to the kitchen, option [b], then option 3. Copied the extracted xip.bin from C:\ELF(in)_Hybrid_Kitchen\Extract_ROM to C:\ELF(in)_Hybrid_Kitchen\Prepare_XIP. Then option 2 in the kitchen. XIP is extracted to the NEW_XIP folder. Then option 1, to copy the new XIP to the C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX\ROM\XIP folder. This comand seems to do nothing, and the old XIP that was already in the destination folder seems to be identical to the new one.

- Option [c] in the kitchen, then option 2. BuildOS tab, then LoadROM button. Then Go button. No errors in the log window, and OS.nb generated in C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX\temp.

- Option [d]. Extended OS.nb size to 50Mb, with oprion 1. Then ran HTCRT with option 3. Clicked button build, chose Elf, chose OS, pointing to the OS.nb file inside C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX\temp, clicked Build!, and created the nbh file.

- Flashed to device.

Well, that´s what I did. Since I didn´t modify anything in the ROM, I suppose I should end up with the same ROM I extracted in the very beginning, but it´s not true. The resulting ROM is missing stuff, can´t active sync, can´t send SMS, etc, etc..

Hope this helps on debugging this kitchen, I already like it a lot, even if not working 100% yet!

Eduardo

[dsixda]

Hi Gartak,

I followed the same steps as you did (in version 1.3.1) and had the same issues. So I guess Koko's new update didn't fix it?

I'm using Hypercore now but it's kind of outdated for some of the stuff I want to do (e.g. SYS and XIP extracting from newer HTC models).


In this case, I have no clue on what may be wrong. I´ll describe in detail what I´m doing, hope someone can help me find what´s going wrong:

- After decompressing the archive and running de setup batch file, ran the shortcut in the desktop to start the kitchen.

- Chose [a] option, then copied TESS 1.9D (NBH file) to the C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\BaseROM folder, and hit option 1.

- Then I copied folders OEM and SYS from C:\ELF(in)_Hybrid_Kitchen\Extract_ROM to C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX

- Back to the kitchen, option [b], then option 3. Copied the extracted xip.bin from C:\ELF(in)_Hybrid_Kitchen\Extract_ROM to C:\ELF(in)_Hybrid_Kitchen\Prepare_XIP. Then option 2 in the kitchen. XIP is extracted to the NEW_XIP folder. Then option 1, to copy the new XIP to the C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX\ROM\XIP folder. This comand seems to do nothing, and the old XIP that was already in the destination folder seems to be identical to the new one.

- Option [c] in the kitchen, then option 2. BuildOS tab, then LoadROM button. Then Go button. No errors in the log window, and OS.nb generated in C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX\temp.

- Option [d]. Extended OS.nb size to 50Mb, with oprion 1. Then ran HTCRT with option 3. Clicked button build, chose Elf, chose OS, pointing to the OS.nb file inside C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX\temp, clicked Build!, and created the nbh file.

- Flashed to device.

Well, that´s what I did. Since I didn´t modify anything in the ROM, I suppose I should end up with the same ROM I extracted in the very beginning, but it´s not true. The resulting ROM is missing stuff, can´t active sync, can´t send SMS, etc, etc..

Hope this helps on debugging this kitchen, I already like it a lot, even if not working 100% yet!

Eduardo

[Gartak]

I tried Hypercore, but to start with, I have no idea on which device to use, since it doesn´t support Elf directly.. Any tips for me?

Thanks!

Eduardo

[kokotas]

In this case, I have no clue on what may be wrong. I´ll describe in detail what I´m doing, hope someone can help me find what´s going wrong:
...
These are some (I'll add more info later on) steps for setting up the kitchen , creating a Base for Cooking and building your ROM:

*.Install Microsoft Visual C++ 2008 Redistributable Package!
**.Install MS .NET Framework!

1.Download the archive which is PART 1!

2.If any previous version exists, DELETE it from your C:\DRIVE! Remove any Desktop Shortcuts too!

3.Extract the archive to C:\DRIVE!

4.Browse to C:\ELF(in)_Hybrid_Kitchen\ and run First_Run_For_ELF(in)_Hybrid_Kitchen.bat.(Now you have 2 shortcuts created on your Desktop)

5.Lets say you want to use a SHIPPED or DUMPED (NOT a COOKED!) ELF(IN) ROM as a Base.
--5.1.Double click the desktop-shortcut "ELF(in)_Hybrid_Kitchen"
--5.2.Press [a]
--5.3.A window pops up beside the DOS screen. Place in there the RUU_Signed.nbh or the OS.nb!
--5.4.Press [1]
--5.5.When the process is completed and pressing any key returns you to main menu, you get another window opening with the 3 folders you want
OEM
SYS
XIP
--5.6.Keep that window open and double click the desktop-shortcut "ELFIN_DEV_v2.1_Build_19XXX"
--5.7.Copy OEM and SYS to C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX\
--5.8.Copy XIP to C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX\ROM\ , but First DELETE(or MOVE elsewhere) the existing XIP folder in there!

6.The Base for cooking your ROM is set! Either clean up the OEM folder from things you wish to be removed or just (re)build the ROM.
--6.1.Double click the desktop-shortcut "ELF(in)_Hybrid_Kitchen" (if you closed the main menu window)
--6.2.Press [c] - Have in mind that for this option ALL packages you want to put inside your ROM should be in the "SYS" folder and NOT in the "Packages" folder!
--6.3.Press [1]
--6.4.BuildOS starts. Select the shown packages(if any)to include in ROM and press the "play" button. When it finishes press "exit".
--6.5.When this process is completed you'll have your OS.nb inside the "temp" folder and you'll be returning to main menu again.

7.Press [d]
--7.1.Press [3] - If your OS.nb is larger than 50MB!
--7.2.Follow the instructions on the DOS screen and in seconds you'll have the (flashable) RUU_Signed.nbh ready.
--7.3.Press [4] to return to main menu.

8.Press [e]
--8.1.Follow on screen instructions and choose flashing method.

---------------------------------------------------------------------------------------------------------------------------------
Now, I have tested the fixed version this morning with my dumped ROM and it worked!
ActiveSync - OK!
Theme changing - OK!
Missing elements - NONE!
Wifi - OK!
Phone - NOT TESTED!
Today Items OK!
I'm thinking to test it again now, but I have only one device and I need it...But I will retest it! If in any case this doesn't work, I have uploaded a base(actually the baseROM I use lately)for you in the Rapidshare folder.
BTW the problem was ONLY in extracting OEM&SYS from Elf(in) ROM as far as I saw! Did anyone discover anything else?

---------------------------------------------------------------------------------------------------------------------------------
I tried Hypercore, but to start with, I have no idea on which device to use, since it doesn´t support Elf directly.. Any tips for me?

Thanks!

Eduardo
Check Installing HyperCore Kitchen for ELF (http://forum.xda-developers.com/showpost.php?p=1574779&postcount=33).
Regards!

[dsixda]

I tried Hypercore, but to start with, I have no idea on which device to use, since it doesn´t support Elf directly.. Any tips for me?

Thanks!

Eduardo

It supports Elf but you have to get the files from Noonski's Cooking Class thread.

[Gartak]

--5.5.When the process is completed and pressing any key returns you to main menu, you get another window opening with the 3 folders you want
OEM
SYS
XIP


Koko, I think I isolated the problem here, but still don´t know how to solve it.

The executable dumprom.exe, in C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\Tools, doesn´t run on my computer. It says: "The system cannot execute the specified program."

This happened before with other commands, but installing the VC++ redist package solved it. However, this time, I already reinstalled VC++ redist, MS Framework 1.1 and 2.0, but the problem persists with dumprom.exe.

I think this is the reason for me to get an empty XIP folder. I´m now installing framework 3.5, but since it takes ages to download and install, I thought it would be better to report the problem before that. I´ll test again when I have framework 3.5 installed.

Thanks!

Eduardo

[AngelDeep]

This happened before with other commands, but installing the VC++ redist package solved it. However, this time, I already reinstalled VC++ redist, MS Framework 1.1 and 2.0, but the problem persists with dumprom.exe.



Install VC 2005 SP1

And, why five files are differents in
C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX\TOOLS
C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\Tools
??

Thanks

[Gartak]

Installed Framework 3.5 and dumprom.exe worked!

Koko, it may be a good idea to state in the first post that Framework 3.5 is needed for this kitchen, to avoid confusion.

I´ll keep testing, and will report soon.

Thanks.

Eduardo

[Gartak]

Did some more testing, closely following Koko´s guide, and here are the results:

1 - Dumping and rebuilding TESS 1.9D ROM: everything worked ok until the OS.nb creation. Got the same problem with both Ervius and Bepe tools: missing file boot.rgu inside XIP folder. Had no idea what to do to fix that, so I gave up.

2 - Dumping and rebuilding official WWE 2.20.707.1B ROM: with this ROM, everything went smoothly from beginning to the end (this time the boot.rgu file got extracted in the XIP folder). However, after flashing this ROM to the device, I noticed it had problems too: couldn´t change themes, the cube was all strange (missing images), couldn´t create connections, missing Office Mobile, missing Device Information icon, couldn´t connect to WiFi, etc, but the phone and active sync worked well. By the way, the device didn´t run the initial customization process after hard reset, as it use to do with this ROM.

Now I´ll try to figure out how to use the dump kokotas uploaded for us.

Thanks guys!

Eduardo

[ayyu3m]

thankx kokotas :D

your' doing a good job updating this kitchen. i had some issues with the 1.3. had some probs while porting the XIP. i looked at the updated bugfixes and updated my kitchen with 1.3.2 as well and now no problems occur when porting the XIP.

plus, thankx for the new XIP 20721 included!!

[dsixda]

Koko,
I'm sorry to say but it's still not working when I use my own ROMs. I rebuilt them without changing anything, but still I get all Today items selected, missing shortcuts, can't change theme, etc. :( Have to go back to Hypercore for now.

[kokotas]

Guys
Thank you very much for giving this a chance to get better by testing it!
I'm sorry that it doesn't work so well for now!
As I said before it would be better to use Hypercore for extracting an ELF(in) ROM and get the OEM & SYS of it,
in order to use it as a base for cooking in this kitchen, or continue and use the building part of Hypecore (but some tools in there are old versions).
Today I have some spare time so I'll look into it!
Your help is appreciated:) - Cause I'm no expert - I just believe that everything is possible - Even more if we work together!

Regards!

[dsixda]

So do you mean that the extraction part is not working 100%, but the building part is ok? In that case I can try using Hypercore to get OEM/SYS/ROM, and then move it all over to Hybrid for the rest of the work.


Guys
Thank you very much for giving this a chance to get better by testing it!
I'm sorry that it doesn't work so well for now!
As I said before it would be better to use Hypercore for extracting an ELF(in) ROM and get the OEM & SYS of it,
in order to use it as a base for cooking in this kitchen, or continue and use the building part of Hypecore (but some tools in there are old versions).
Today I have some spare time so I'll look into it!
Your help is appreciated:) - Cause I'm no expert - I just believe that everything is possible - Even more if we work together!

Regards!

[kokotas]

So do you mean that the extraction part is not working 100%, but the building part is ok?

That's exactly what I mean man:)
Try it yourself...

In Hypercore:
1.Dump the ROM
2.Make Packages with PKGTool

Move OEM and SYS folders into the Hybrid.

In Hybrid:
Just Mix&Cook your ROM

*Regarding the XIP:
If you tried already to dump the same ROM in Hybrid, you should have the XIP folder ready to use,
so you could use it for the building part by placing it inside the ROM folder!

The problem with this "kitchen" is the generated OEM&SYS folders after dumping an ELF(in) ROM!
And it's really strange cause those files are identical to the files that Hypercore gives...:confused:
Still working on it!

Regards!

[kokotas]

Still working on it!
ps:If it doesn't work this time too, then I'll have to put it on hold till the end of the month cause of busy schedule.
Hope you understand...
Well, I lied:)
I tried one more time and I did it.
I dumped - rebuilt and flashed successfully my dumped ROM, one Shipped ROM and that Orange 2.27 ROM without any issues!
Test it please!
I just hope I uploaded the correct archive and not the old one!:oLOL:D
Cause I did not change the version - I forgot it!:o
Regards!

[dsixda]

Well, I lied:)
I tried one more time and I did it.
I dumped - rebuilt and flashed successfully my dumped ROM, one Shipped ROM and that Orange 2.27 ROM without any issues!
Test it please!
I just hope I uploaded the correct archive and not the old one!:oLOL:D
Cause I did not change the version - I forgot it!:o
Regards!

Hey dude,
Will this do automatic relocating of SYS/XIP? I spent all night trying to do that on Hypercore LOL..

[kokotas]

Hey dude,
Will this do automatic relocating of SYS/XIP? I spent all night trying to do that on Hypercore LOL..
Regarding the SYS:
Yes, it will - if you use a .VM folder from a (*better be original) ELF(in) rom, and NOT from another device!

Regarding the XIP:
If you're dumping an ELF(in) rom, as you've seen, you get the XIP folder(with the modules,etc)ready to use for building!
[But if you feel that relocating those modules would affect performance or something, do so by pressing [b] @ the main menu window and follow instructions.(Optional)]

If you're dumping the rom from another device, you get only the xip.bin which should be used in the next step...
which is [b] @ the main menu window and follow instructions for relocating the XIP modules!

[dsixda]

DUDE...

It works now!!!! Congrats! What did you change?

I simply extracted and rebuilt my base ROM without making any changes, and after I flashed it, it was the same as it was before :)

Now to start porting and cooking!!!!!

[shafez]

kokotas

I have followed all instructions.

-Extracted Kaiser WM6.1 Rom version 3.28.405.0
-Used the Extracted XIP.bin to dump the XIP using Option "b"
-Extracted ELFin Rom version 2.21.415.2B
-Relecoated the Kaiser SYS folder
-Used the ELFin OEM Folder
-When I Build the rom I get the Following Error:

BUILDXIP 0.54 Copyright (c) 2007-2008 bepe 30 Jan 2008

ERROR! (errorlevel: -1073741819)
Press any key to continue . . .

Now if I use the Elfin XIP which was Extracted by the kitchen, Everything works fine and I was able to flash the ROM.

But the XIP's are not WM6.1, It is WM6.

I have used all the 3 options in option "b" to extract the XIP and still got the same Error.

Please advice.

Best Regards

[kokotas]

DUDE...

It works now!!!! Congrats! What did you change?
Just found where the problem was and hitted it on the head:D
Well, I reorganized the tools and edited the bat file to avoid copying and recopying where it wasn't necessery.
Now to start porting and cooking!!!!!
Good to hear that! Happy cooking man!
kokotas

I have followed all instructions.

-Extracted Kaiser WM6.1 Rom version 3.28.405.0
-Used the Extracted XIP.bin to dump the XIP using Option "b"
-Extracted ELFin Rom version 2.21.415.2B
-Relecoated the Kaiser SYS folder
-Used the ELFin OEM Folder
-When I Build the rom I get the Following Error:

BUILDXIP 0.54 Copyright (c) 2007-2008 bepe 30 Jan 2008

ERROR! (errorlevel: -1073741819)
Press any key to continue . . .

Now if I use the Elfin XIP which was Extracted by the kitchen, Everything works fine and I was able to flash the ROM.

I have used all the 3 options in option "b" to extract the XIP and still got the same Error.

Please advice.

Best Regards
Hey shafez!
As you have realized yourself, the problem is with the XIP.
From the main window follow these steps:

- Port over any XIP to your device(you need xip.bin)

------ [1] - Make NEW_XIP using XIPPort-XIPAddrTools(fast)

*********Place the xip.bin inside the opened window*********

------------ [1] - Dump Kaiser,Diamond,Polaris,Xperia ... XIP

**************Follow onscreen instructions regarding XIPPort**************
**************Follow onscreen instructions ([B]1-6,not 7) regarding XIPAddrTools**************
* Also, If a module can not be relocated, ignore it too for now.*
* Later on, you could overwrite it by the matching module.*
While you relocate the modules, you see that some of them cannot be relocated(like initvmmap.exe, filesys.exe, nk.exe).
Leave XIPAddrTools running.
Open the Work_XIP_OUT and remove those modules(&modules.txt) that don't get relocated.
Either continue to the next step as you are OR copy the matching modules from the Ref_XIP_OUT into the Work_XIP_OUT.
The next step is returning to XIPAddrTools (which runs already) to repeat everything:
Select Work Folder
Select Reference Folder
Check now if there are any conflicts..
If everything is ok follow instruction 7 and continue.
Hope I didn't confuse you:)
But the XIP's are not WM6.1, It is WM6.
If you just want the core of WM6.1 you could use the XIP provided with the kitchen.
But if you like porting,cooking&headaches:p try porting the XIP from the rom you talked about!
Here is also a link to get more info about porting&cooking:XIP & SYS Porting Guide (http://forum.xda-developers.com/showthread.php?t=379598)
Regards!

[shafez]

Dear kokotas

Thank you for all the effort you have put in this Kitchen.

My problem was as that I was using the XIP.bin which is generated when using option "a" to dump the Kaiser Rom.

There seem to be a problem in the kitchen when it comes to dump the xip from other devices.

I have used the kaiser kitchen to dump the kaiser kithcen and them used the XIP which was generated.

I used the the ELFin Kitchen option "b" to dump the xip and selected option "3" which is do it the easy way.

It worked ok and I was able to build the rom using your kitchen.

Again thank you for all the work and support

Best Regards.

[humrod]

Hi friends: I'm instaling the kitchen. Follow the steps but at the end (after run first time bat) the acceses in the desktop don't appear. I tried to start the kitchen manually (by running the direferent .bat) but nothing happens. can you help me, please

[kokotas]

Hi friends: I'm instaling the kitchen. Follow the steps but at the end (after run first time bat) the acceses in the desktop don't appear. I tried to start the kitchen manually (by running the direferent .bat) but nothing happens. can you help me, please
Hey humrod!
Are you running WinXP or Vista?
The "first time" bat should create 2 shortcuts on your desktop regardless of anything else!
Are you sure that you have the ELF(in)_Hybrid_Kitchen folder under your C: Drive?

[humrod]

Thanks for your comment. Yes the folder is in C: I'm using xp. In fact i reinstall 3 times and you can see the dos window work, but the access don't create. maybe could be that i use de Documents and settings in a diferent partition?
BTW, i'm looking for the nikmel tutorial you mentioned in the first post for extend the size of the OS or the NBH, but can't found it. have a link or a place to look?

[kokotas]

Thanks for your comment. Yes the folder is in C: I'm using xp. In fact i reinstall 3 times and you can see the dos window work, but the access don't create. maybe could be that i use de Documents and settings in a diferent partition?
I guess that's the reason!
You could copy-paste the shortcuts from the Batch folder on your desktop.
BTW, i'm looking for the nikmel tutorial you mentioned in the first post for extend the size of the OS or the NBH, but can't found it. have a link or a place to look?
Check rollup thread/post4/12. Modifying&Cooking stuff/Link11
Regards!

[humrod]

Thank you so much for your response. I didn't know about the page in elf accesories. BTW i resolve the problem extracting all the stuff in C: run the .bat and after, moving the folders to the general folder of the kitchen.

[humrod]

Hi folks!
I'm trying to translate many roms, but ever with the same situation: After flash, pass from first splash sceeen to Today, without the alignment screen and any of the others (date, etc) Of course the screen isn't aling and can't enter in today menu.
I follow the steps:
1) Change the 0409 MUI by modificated spanish 0409 MUI
2) Edit Initflashes.dat and delete the 2 first bytes (hexedit)
3) Change some especific names in registry
4) Change the folders name in registry
I miss something?

[kokotas]

I can't really help you cause I've never translated my rom, but what you've done so far is only one way to translate a rom. And it is a dirty way!
There should be another way-more clean.
Some experts(eg: pkoper or gullum)could help you since they've published roms in other langs.
But you could also dump a nonWWE original rom&see the structure, compare files&registry&move on from there...
Regards!

[kokotas]

How about a CustomRUU?
Does anyone find it useful?
Looks like this:

http://i279.photobucket.com/albums/kk145/k0k0tas/customruu01.jpg

http://i279.photobucket.com/albums/kk145/k0k0tas/customruu02jpeg.jpg

Any suggestions?

Regards!

[Taninpv]

Hi Kokotas,
Please take a look at the two screens One is yours and two is my.

#1
http://i279.photobucket.com/albums/kk145/k0k0tas/screen1.jpg

#2
http://forum.xda-developers.com/attachment.php?attachmentid=118967&d=1223220625


I just downloaded the files from post #1, installed as instructed. BUT???
This is the screen that wouldn't allow me to keyboard input one of the options.

[!Aman!]

i guess u are looking for option to dump opal's ROM. the method to dump opal's ROM is similar to Elf(in) ROMs except for the xip.bin

[Taninpv]

Ok.
Trying to cook my own rom with selected programs for my personal use.
According to this dos command screen, right after I dumped the *nbh

Your BASE for COOKING is ready!
NEW OEM, SYS and XIP(only if you used *.nbh or *.nb)are generated into
C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\Temp
Next time you run this program these will be erased!
Move them to C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX
in order to have a BASE to start cooking

Do I move the file called "Packages" to ELF(in)_Hybrid_Kitchen\ELFIN_DEV_V2.1_Build_199xx? Because in this directory, there are :
OEM: (empty)
Packages: (BuildDsm) and (DSMBuilder)
SYS: (empty)

If I move the "Packages" over to this directory, it will overwrite the two existing files inside Packages:
Or should I just copy/paste the OEM/SYS to this directory and not to touch the folder "Packages"?

[!Aman!]

u need to move OEM and SYS for sure. although packages directoty is not necessary if there is no OEM package inside it.

[kokotas]

Ok.
Trying to cook my own rom with selected programs for my personal use.
According to this dos command screen, right after I dumped the *nbh

Your BASE for COOKING is ready!
NEW OEM, SYS and XIP(only if you used *.nbh or *.nb)are generated into
C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\Temp
Next time you run this program these will be erased!
Move them to C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX
in order to have a BASE to start cooking

Do move the file called "Packages" to ELF(in)_Hybrid_Kitchen\ELFIN_DEV_V2.1_Build_199xx? Because in this directory, there are :
OEM: (empty)
Packages: (BuildDsm) and (DSMBuilder)
SYS: (empty)

If I move the "Packages" over to this directory, it will overwrite the two existing files inside Packages:
Or should I just copy/paste the OEM/SYS to this directory and not to touch the two files inside Packages?

NEW OEM & SYS are in C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\Temp\Package s

Copy those OEM & SYS folders and paste them to
C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX
overwriting the empty folders there.

Your base for cooking is ready!

If you want to cook exactly the same os that you're dumping(ONLY FOR ELF(in) case)
then copy the XIP folder from C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\Temp to C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX\ROM overwriting the XIP folder in there.

I hope I didn't confuse you..
Regards!

[Taninpv]

u need to move OEM and SYS for sure. although packages directoty is not necessary if there is no OEM package inside it.
Thanks htctouchp. I thought so, and that is what I did.
Hey, where can I find the Alarm5: rooster crowing and blackkeyboard from your Tessv2.5? I really love it. Don't think I want to use Opalkeyboard.

[Taninpv]

NEW OEM & SYS are in C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\Temp\Package s

Copy those OEM & SYS folders and paste them to
C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX
overwriting the empty folders there.

Your base for cooking is ready!

If you want to cook exactly the same os that you're dumping(ONLY FOR ELF(in) case)
then copy the XIP folder from C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\Temp to C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19X XX\ROM overwriting the XIP folder in there.

I hope I didn't confuse you..
Regards!

Not at all, Kokotas. Your instruction is great. I am a slow learner, and just making sure to dot the I and cross the T. :D:D

[!Aman!]

Thanks htctouchp. I thought so, and that is what I did.
Hey, where can I find the Alarm5: rooster crowing and blackkeyboard from your Tessv2.5? I really love it. Don't think I want to use Opalkeyboard.
u can get them from my ROM v1.9D...dump it and get them from there. for black keyboard, just use msim.96.dll.

[Taninpv]

u can get them from my ROM v1.9D...dump it and get them from there. for black keyboard, just use msim.96.dll.

Thanks, will do. :D

[kpshamilsagar]

hi...when i try 2 create oem from cab..on the 4th stage when i close packages creator.it shows the error mentioned below on the picture...n the next window named as "initflashfiles tab" is not coming n its going 2 de previous window(package creator) any1 tel me wts de real problem???pls help me....

[Taninpv]

kokotas/htctouchp (or any expert)

Can one of you please review this log.txt from my rom built?

If you could help me out with my log reading. Would appreciate very much for your help.

[!Aman!]

kokotas/htctouchp (or any expert)

Can one of you please review this log.txt from my rom built?

If you could help me out with my log reading. Would appreciate very much for your help.
there is nothing really in the log file. it just shows the processing of dsm's and rgu's by BuildOS.exe and later on the rgu's processed by rgucomp.exe on all the rgu's to build the hives.
any problems in cooking?

[Taninpv]

Hi htctouchp,
Yeah, I was using your Tess v1.9D OEM, SYS from Opal, and XIP from Opal.
I also use some of your great features; like loud volumn, black keyboard(didn't like Opal keyboard), total command, and other great programs.

My first attempt was a failure. Guess I will try again.

[kokotas]

My first attempt was a failure. Guess I will try again.
That's the spirit!
I have messed up my kitchen files too many times to remember:D
but the cooking&flashing addiction wins all the time!
Something that you should be careful is not to change many things at once(eg.XIP&SYS&OEM simultaneously) cause then you won't be able to track the mistake(if any)!
Also (an advice that htctouchp gave me once & I followed it) when you reach to the point of cooking a ROM that flashes ok and runs smooth, make a dumpable *.nbh and back it up for just in case, cause you save your cooking base in that way;)!

Finally, I'd like to say that a new version is up on 1st post!

Regards!

[Taninpv]

Very clever...

Thanks for the new Hybrid.:D

[dsixda]

Kokotas,

I'm still using the same version from over a month ago. I noticed a trojan detected by AVG, and am not sure if it just a false alarm:

C:\ELF(in)_Hybrid_Kitchen\Prepare_UPX\upx.exe

It says the file is a Trojan horse Generic11.AYBA

[kokotas]

Hey dsixda!
I don't use antivirus, but I think it's a false alarm!
Here is the link where I got the UPX: http://upx.sourceforge.net/
You could download it separately and check again..
Regards!

[niceguy001]

first, thanks for putting effort on creating and assembling this kitchen.
as a bignner it's not that easy to use this kitchen. i did lots of reading but still not in a position to cook my own rom.I wonder how Microsoft or it's Partners deploy/cook/prepare it on the devices. maybe i have missed something in order to understand things fully. maybe some tips & infos can help me. if i could get to know how cooking and porting system work, i could have been writing a fully GUI for this kitchen.

thanks ya all

[cacahahacaca]

In case anyone was still interested, I was able to extract the rooster alarm sound by using kokotas' wonderful kitchen tools.

You can find the file (and the procedure I followed) starting at post 2356 here:

http://forum.xda-developers.com/showthread.php?t=415880&page=236

[trueg]

viewdetail.exe under Tools keeps coming up as a Trojan (TR/Crypt.XPACK.Gen) with AntiVir. Can I delete this file, do I need it for anything?

[kokotas]

viewdetail.exe under Tools keeps coming up as a Trojan (TR/Crypt.XPACK.Gen) with AntiVir. Can I delete this file, do I need it for anything?
Better delete the AntiVir.:p
I'm joking..:D
If you delete the viewdetail.exe you won't have any cooking problems-it is not essential-but you won't get the size of your rom displayed.That's all!

Regards!

ps:New version is coming up soon...

[ksk622]

Question deleted.

[kokotas]

I missed a lot of action the last days, so here I am trying to catch up:D
ELF(in) Hybrid Kitchen V1.4.2(BETA)
ELF(in) Hybrid Kitchen V1.4.2(BETA) - Includes Fix1
ELF(in) Hybrid Kitchen V1.4.2(BETA) - Includes Fix1&2 (http://forum.xda-developers.com/showpost.php?p=2326139&postcount=1)

Regards!

[!Aman!]

I missed a lot of action the last days, so here I am trying to catch up:D

yes indeed :D, u've got a lot of things to catch up ;)

[swordfish2009]

Tried your last beta.. boot.rgu is not extracted .. Also didnt find xip-out.bin
So first option in build menu is not possible..

[kokotas]

Tried your last beta.. boot.rgu is not extracted ..
What do you mean?
When dumping a rom?
Also didnt find xip-out.bin
So first option in build menu is not possible..
You have to build xip_out.bin with XIPPort
or if have the out.bin from the previous version(inside /ROM)
rename it to xip_out.bin and use that..

[swordfish2009]

yes... it is not extracted during dumping

Just now i found that xip_out.bin is to be build .. my bad...
I dont have any out.bin in /ROM .
Last its giving some .net unhandled exception while dumping xip.bin is in progress.. "offset and length were out of bound for the array.."

When i try to build the rom with 2nd option, it says "program needs administritive permission", and when i run the batch file as administrator then it cmd windoz doesnt start at all

[kokotas]

yes... it is not extracted during dumping
Replace the DumpNBH.bat&Port_XIP.bat in ELF(in)_Hybrid_Kitchen\Batch\ with the attached ones and try again..

EDIT:The uploaded kitchen is updated with these new bats.

Last its giving some .net unhandled exception while dumping xip.bin is in progress.. "offset and length were out of bound for the array.."
When i try to build the rom with 2nd option, it says "program needs administritive permission", and when i run the batch file as administrator then it cmd windoz doesnt start at all
Have you installed on your pc Microsoft Visual C++ 2008 Redistributable Package and Microsoft .NET Framework 3.5?

[swordfish2009]

I will give a try..
EDIT : Still no boot.rgu in XIP folder.

For 2nd prob, yups i have installed both..

[kokotas]

I will give a try..

For 2nd prob, yups i have installed both..
Thanx for the feedback man!
For the 2nd prob, I can't think of any other reason now..But I am sure there is a solution since both options for building the OS are working fine on my pc!
Have to go to bed..

Regards!

[swordfish2009]

Thanks mate.. me too want to go to bed now... gudnite..

[ayyu3m]

New Version - Check ChangeLog
ELF(in) Hybrid Kitchen V1.4.2(BETA)
ELF(in) Hybrid Kitchen V1.4.2(BETA2) - Includes Fix1
ELF(in) Hybrid Kitchen V1.4.2(BETA3) - Includes Fix1&2 (http://rapidshare.com/files/163545446/ELF_in__Hybrid_Kitchen_V1.4.2_BETA_.7z)

This is BETA, so please test and help make any fixes...

Fixes(extract them in ELF(in)_Hybrid_Kitchen\Batch\):
Fix1 (http://forum.xda-developers.com/attachment.php?attachmentid=129367&d=1226529180) - DumpNBH.bat
Fix2 (http://forum.xda-developers.com/attachment.php?attachmentid=129681&d=1226621637) - Port_XIP.bat

(The old version is still here - below posts)
nice! jus what i need as i m having some unknown problem related to building OS.nb using the OEM, SYS and XIP of the ELFIN 3.07

the problem...i ported XIP using this kitchen bro..but after os.nb.payload is copied...the ImgfsFromNb.exe gives an error in vista

is this problem solved in this new beta bro???

[ayyu3m]

EDIT: trying the 1.4.2 BETA...and WOW! you completely re-done the setup. i jus extracted 3.07 .nbh and the the SYS and OEM are created inside Packages folder...and you also added mrvanx SYS info tool

great going bro...now i officially declare myself as a beta tester for this kitchen...gonna try all the functions to see if its up and running the way you plan it to be

so now i m off to XIP porting and hopefully to build OS

[ayyu3m]

here i go again. WOW!!!

this time..its out of curiosity too.

cos i m seeing after the xip.bin has been extracted i dont get the choice to move it like in the previous kitchen...and so i head over to

ROM\XIP

and see that only boot.rgu is there. but thats fine!

cos \Extract_ROM\Temp\XIP is also there and \Prepare_XIP\NEW_XIP

but now i see a new folder called NULL @ ROM\NULL where all the contents are copied to??

so now i m thinking from which folder does the XIP moves from...and i assume if i extracted a donor XIP....it wud be read from NEW_XIP and copied over to???

so ultimately the question is, what are the final locations by which XIP is read before OS.nb is built

[ayyu3m]

hmmm...is it me...or this doesnt seem right.

i ported xip.bin which is from Blackstone (Touch HD) and the files get created over NEW_XIP

the kitchen doesnt give me any option to copy the NEW_XIP to my \ROM\XIP

and when i want to build OS...this is the first warnings i get..

Rearranging files inside ROM folder...
A duplicate file name exists, or the file
cannot be found.
A subdirectory or file XIP already exists.
The system cannot find the file specified.

Creating 'dump' folder...


did the XIP from blackstone got ported to my ELFIN???

:D

yep! the last 3 posts were mine, pls excuse me...but this is all in the name of cutting the curiosity over the NEW beta which i m trying

hehe

[kokotas]

Hey Bro!
now i officially declare myself as a beta tester for this kitchen...gonna try all the functions to see if its up and running the way you plan it to be
That's great!I'll need all the help I can get..cause there are significant changes!
here i go again. WOW!!!
this time..its out of curiosity too.
cos i m seeing after the xip.bin has been extracted i dont get the choice to move it like in the previous kitchen...
I removed the option to copy NEW_XIP to ROM folder - you just have to do that manualy:)
and so i head over to
ROM\XIP
and see that only boot.rgu is there. but thats fine!
In this version of the kitchen the XIP folder is also empty like OEM&SYS in order to use yours.
cos \Extract_ROM\Temp\XIP is also there and \Prepare_XIP\NEW_XIP
but now i see a new folder called NULL @ ROM\NULL where all the contents are copied to??
so now i m thinking from which folder does the XIP moves from...and i assume if i extracted a donor XIP....it wud be read from NEW_XIP and copied over to???
so ultimately the question is, what are the final locations by which XIP is read before OS.nb is built
If you select option 1 in building your ROM the files in XIP folder are copied to a new folder NULL and only boot.rgu is kept inside XIP.
But that's because option 1 in building your ROM requires the following files in ROM folder:
XIP(folder) including ONLY boot.rgu
OS.nb.payload
xip_out.bin(built with option 1 in XIP Porting)
hmmm...is it me...or this doesnt seem right.
i ported xip.bin which is from Blackstone (Touch HD) and the files get created over NEW_XIP
the kitchen doesnt give me any option to copy the NEW_XIP to my \ROM\XIP
and when i want to build OS...this is the first warnings i get..
Rearranging files inside ROM folder...
A duplicate file name exists, or the file
cannot be found.
A subdirectory or file XIP already exists.
The system cannot find the file specified.
Creating 'dump' folder...

did the XIP from blackstone got ported to my ELFIN???
No it didn't..because in order to use the NEW_XIP you have to copy it to ROM\ and select option 2 in building your rom, which is the only option for this version that uses bepe's buildxip.exe

:D
yep! the last 3 posts were mine, pls excuse me...but this is all in the name of cutting the curiosity over the NEW beta which i m trying
hehe
No problem man!
I should have made the changes more clear from the beginning:D

As a conclusion here is what you should have in mind:
Option1 in XIPPorting leads to Option1 in BuildingROM(Doesn't require the usual XIP folder)
Option2 in XIPPorting leads to Option2 in BuildingROM(Requires the usual XIP folder)

Regards!

[ayyu3m]

hehe. you took the time to organize and answer all my doubts. so this is one kitchen i m gonna indeed enjoy helping out with. gonna check porting a rom now

thankx bro

[swordfish2009]

Man, I think this kitchen is not vista competible..
Ayyu3m, which OS do you use?

When i try to extract the .nbh file with 2nd option then some imgfsto... stops working and crashes..
also while building rom it gives that you need administrators permision..
and if I start trting the kitchen with admin permission then it never starts..

Any vista user having proble?

[ayyu3m]

Man, I think this kitchen is not vista competible..
Ayyu3m, which OS do you use?

When i try to extract the .nbh file with 2nd option then some imgfsto... stops working and crashes..
also while building rom it gives that you need administrators permision..
and if I start trting the kitchen with admin permission then it never starts..

Any vista user having proble?
i m using Windows Vista with USER ACCESS CONTROL turned OFF


that my friend...is the root of all ur probs, as the kitchen is highly dependent on dll that needs to run freely and automated without any control restricting them

try with UAC turned OFF

:D

[kokotas]

Man, I think this kitchen is not vista competible..
Any vista user having proble?
The truth is that it's never tested on Vista!
I'll try it on Vista when I get the chance&report back..
But I think(&hope)that it's not a Vista compatibility issue here..
EDIT:Try what ayyu3m suggested&see if the problem persists.
Regards!

[ayyu3m]

also i presume u have already installed

Microsoft Visual C++ 2008 Redistributable Package and Microsoft .NET Framework 3.5

as suggested by koko and applied the fixes

[swordfish2009]

Yes I will try switching it off.. Its annoying option..

I have installed Microsoft Visual C++ 2008 Redistributable Package and Microsoft .NET Framework 3.5..

Will check tonite..

[ayyu3m]

The truth is that it's never tested on Vista!
I'll try it on Vista when I get the chance&report back..
But I think(&hope)that it's not a Vista compatibility issue here..
EDIT:Try what ayyu3m suggested&see if the problem persists.
Regards!
then its good news to you bro...since i have been using ur previous kitchen...namely 1.3...from the start of my cooking...in windows vista home premium and ultimate as well. and as an additional info..on an acer laptop

:D

[swordfish2009]

Man home premium, ultimate.. seems you are rich..

[vadyarik]

kokotas, hi!
File Elf.htcrtproj in your kitchen required modifications: ModelId = Elf010050 should be changed to ModelId = ELF010050. Otherwise ROM is not installed on the device, with Hard-SPL.

[kokotas]

kokotas, hi!
File Elf.htcrtproj in your kitchen required modifications: ModelId = Elf010050 should be changed to ModelId = ELF010050. Otherwise ROM is not installed on the device, with Hard-SPL.
Yes, you're right man! Found that after flashing HardSPL..
That's why the MID & CID in the new version are modified to:
MID: ELF0*****
CID: 11111111

Regards!

[vadyarik]

I only noticed Update :D
Thank you!

[Taninpv]

I was wondering why I could not flash my rom. Keep disconnecting after reboot the previous rom.
Good catch.:D

[trueg]

I say, pretty quick to update to 3.10, but either way 1.4.3 with 3.10 XIP and payload seems to work great. :D

[kokotas]

I was wondering why I could not flash my rom. Keep disconnecting after reboot the previous rom.
Good catch.:D
Yeah, after flashing the HardSPL 3.07, I also wanted to try a ROM (built with MID ELF010050) and it didn't worked!
But then I remembered that cmonex :
...removed modelid patch after determining it wasn't necessary (makes it safer by not allowing to flash other devices' roms).
So that from now&on default MID in (htcrt)kitchen is ELF0*****!

I say, pretty quick to update to 3.10, but either way 1.4.3 with 3.10 XIP and payload seems to work great. :D
Thanx for using v1.4.3.
If this version has no bugs, it will be the final!

Regards!

[VJstar]

Feedback question, I don't know 3.xx xip PP value of the offset is not wrong?

echo.Patching PagePool Size (12MB for ELFin, 4MB for ELF)...
..\TOOLS\hexalter.exe OS.nb 0x045210=3,21 0x045214=4,22

yours value not working.

I find this value from os.nb

echo.Patching PagePool Size (12MB for ELFin, 4MB for ELF)...
..\TOOLS\hexalter.exe OS.nb 0x045178=3,21 0x04517C=4,22

isn't right ?

[trueg]

I say, pretty quick to update to 3.10, but either way 1.4.3 with 3.10 XIP and payload seems to work great. :D

Uh oh, I guess I spoke too soon. I'm not sure how this would happen, but even using the stock 3.10 OEM, SYS and XIP I am not able to change any of the sound settings. Once I enter it I am unable to 'ok' out of it. Also If I try and change the ring tone, once I hit 'ok' it reverts back to default and again it still will not close. Strange. :(

[trueg]

Uh oh, I guess I spoke too soon. I'm not sure how this would happen, but even using the stock 3.10 OEM, SYS and XIP I am not able to change any of the sound settings. Once I enter it I am unable to 'ok' out of it. Also If I try and change the ring tone, once I hit 'ok' it reverts back to default and again it still will not close. Strange. :(

uhh wait, is xip_out.bin simply the xip.bin renamed to xip_out.bin? I'm now guessing not since you have added an option to create an xip_out.bin from the original xip.bin. That would most likely be my problem.

I have attempted to make my own xip_out.bin using your kitchen. I will let you know if that was my problem.

[trueg]

uhh wait, is xip_out.bin simply the xip.bin renamed to xip_out.bin? I'm now guessing not since you have added an option to create an xip_out.bin from the original xip.bin. That would most likely be my problem.

I have attempted to make my own xip_out.bin using your kitchen. I will let you know if that was my problem.

WTF, that wasn't it. :(

I'm using the stock 3.10.710.0 XIP, OEM and SYS with Hybrid 1.4.3. It seemed to dump just fine. It builds fine. It installs without error. Everything seems to work fine, except I can't change any sound options. Once I enter the setting, I can't exit and if I change anything it just reverts back but still won't let me exit. :mad:

[kokotas]

Feedback question, I don't know 3.xx xip PP value of the offset is not wrong?

echo.Patching PagePool Size (12MB for ELFin, 4MB for ELF)...
..\TOOLS\hexalter.exe OS.nb 0x045210=3,21 0x045214=4,22

yours value not working.

I find this value from os.nb

echo.Patching PagePool Size (12MB for ELFin, 4MB for ELF)...
..\TOOLS\hexalter.exe OS.nb 0x045178=3,21 0x04517C=4,22

isn't right ?
If you use OEMXIPKERNEL(particularly nk.exe) from 3.07 or 3.10 ROM and the provided OS.nb.payload, then the address for the pp is correct (starts @ 0x045210).
uhh wait, is xip_out.bin simply the xip.bin renamed to xip_out.bin?
You could use the xip.bin as xip_out.bin.
WTF, that wasn't it. :(
I'm using the stock 3.10.710.0 XIP, OEM and SYS with Hybrid 1.4.3. It seemed to dump just fine. It builds fine. It installs without error. Everything seems to work fine, except I can't change any sound options. Once I enter the setting, I can't exit and if I change anything it just reverts back but still won't let me exit. :mad:
So if I get it right...you just
dumped the 3.10 ROM ,
moved OEM&SYS to \ELFIN_DEV_v2.1_Build_19XXX
moved XIP(folder) to \ELFIN_DEV_v2.1_Build_19XXX\ROM
and
rebuilt your rom with option[2].
It should work without problems!
This is strange!:confused:
In fact, I am porting the 20759 build now and I don't have any problem changing the sounds
and I use the OEM from 3.10ROM!

Regards!

[trueg]

You could use the xip.bin as xip_out.bin.

So if I get it right...you just
dumped the 3.10 ROM ,
moved OEM&SYS to \ELFIN_DEV_v2.1_Build_19XXX
moved XIP(folder) to \ELFIN_DEV_v2.1_Build_19XXX\ROM
and
rebuilt your rom with option[2].
It should work without problems!
This is strange!:confused:
In fact, I am porting the 20759 build now and I don't have any problem changing the sounds
and I use the OEM from 3.10ROM!

Regards!

That's close to what I did. I moved OEM and SYS to ELFIN_DEV.... and I renamed xip.bin to xip_out.bin and moved it to *\ROM. Inside \ROM\XIP is only the boot.rgu that came with the kitchen.

[kokotas]

That's close to what I did. I moved OEM and SYS to ELFIN_DEV.... and I renamed xip.bin to xip_out.bin and moved it to *\ROM. Inside \ROM\XIP is only the boot.rgu that came with the kitchen.
Next time, before flashing, Hard Reset your Touch and replace the boot.rgu in \ROM with the one you have in the dumped XIP (folder).

[Taninpv]

I am having the same problem. I thought it was me, but I am glad to hear that I was not the only one.
With the shipped ROM, I didn't have any problem. But because of the large RAM. I want to remove programs that I don't use, and add programs that I do use. I was using the base ROM from shipped room to cook my own rom.
Well, I just didn't understand why I keep getting stuck on Sounds & Notifications.

[trueg]

I am having the same problem. I thought it was me, but I am glad to hear that I was not the only one.
With the shipped ROM, I didn't have any problem. But because of the large RAM. I want to remove programs that I don't use, and add programs that I do use. I was using the base ROM from shipped room to cook my own rom.
Well, I just didn't understand why I keep getting stuck on Sounds & Notifications.

It's strange because everything else seems to work. Having problems with Sounds & Notifications seems like such an arbitrary place to have a problem.

[trueg]

Next time, before flashing, Hard Reset your Touch and replace the boot.rgu in \ROM with the one you have in the dumped XIP (folder).

So I don't know what happened last time, but I deleted the Kitchen and installed it again. Dumped the 3.10.710.0 NBH. Copied the OEM, SYS and XIP folders over. renamed xip.bin to xip_out.bin and copied it to \ROM. Built it, flashed it and tested it and this time it works fine.

The one difference is I copied over the full XIP folder (files and all) instead of using just the boot.rgu that came with the kitchen.

I also see that it automatically moved all of the XIP files except boot.rgu into \ROM\NULL. I guess in the end, the only difference was using the dumped boot.rgu instead of the one that came with the kitchen. The dumped boot.rgu was slightly bigger, so I guess something was different.

[Demo[95]]

My rom suffured the exact same problem... i updated the kitchen and regenerated everything and now it's working.

Ho btw a guy using my rom (before the correction) told me that beam didn't work too... Trueg, did you experienced that problem too?
Does beam work now for you? (i cannot test for now this feature..)

[trueg]

;2932423']My rom suffured the exact same problem... i updated the kitchen and regenerated everything and now it's working.

Ho btw a guy using my rom (before the correction) told me that beam didn't work too... Trueg, did you experienced that problem too?
Does beam work now for you? (i cannot test for now this feature..)

I couldn't say, I never use that feature.

[VJstar]

If you use OEMXIPKERNEL(particularly nk.exe) from 3.07 or 3.10 ROM and the provided OS.nb.payload, then the address for the pp is correct (starts @ 0x045210).

You could use the xip.bin as xip_out.bin.


Regards!


yes,i'am sure .i used OEMXIPKERNEL and all of xip.bin form 3.07 CHT. i find PP patch address is correct (starts @ 0x045178 for ELFIN , 0x04517C for ELF )
why ?

[!Aman!]

i've another method for u guys to change the PP. search the 03 15 A0 03 02 15 A0 13 00 10 83 E5 62 C2 FF EB in yours S000 of nk.exe and change the string marked in Red color to 00 00 A0 E1. from there onwards u can simply use the old Multi-platform PP changer.exe (that is also found in kaiser kitchen) to change ur PP on the OS.nb. this should make the kitchen even simpler :D

PS: this method works regardless of the device.

[VJstar]

i've another method for u guys to change the PP. search the 03 15 A0 03 02 15 A0 13 00 10 83 E5 62 C2 FF EB in yours S000 of nk.exe and change the string marked in Red color to 00 00 A0 E1. from there onwards u can simply use the old Multi-platform PP changer.exe (that is also found in kaiser kitchen) to change ur PP on the OS.nb. this should make the kitchen even simpler :D

PS: this method works regardless of the device.

Thx bro.I just do it... i uesd xip.bin all of for 3.10 Aus rom this time,i find 0x045210 and 0x045214 ..hehe.... but cht 3.07 why not ?

but i find new question this time.. i lost 3rd sceen pitcure and themes... i think xip have problem.... who can tell me why? i just remove hd.dll osaxst0.dll mencfilt.dll and boot_ms.rgu

[!Aman!]

Thx bro.I just do it... i uesd xip.bin all of for 3.10 Aus rom this time,i find 0x045210 and 0x045214 ..hehe.... but cht 3.07 why not ?

but i find new question this time.. i lost 3rd sceen pitcure and themes... i think xip have problem.... who can tell me why? i just remove hd.dll osaxst0.dll mencfilt.dll and boot_ms.rgu
if the device goes past the main splash screeen then xip doesn't have a problem. also u can remove those modules (hd.dll etc) without a problem.

[VJstar]

if the device goes past the main splash screeen then xip doesn't have a problem. also u can remove those modules (hd.dll etc) without a problem.

I forgot that I was the third screen into the theme of oem to use. Perhaps the problem could appear in the paper dsm.

the dsm is empty...dsm document is not associated with any documents

[VJstar]

I found the problem, when I use all_packages_to_one, the occurrence of such a loss. :confused::confused:

TOOLS\all_packages_to_one > nul
del buildpkg.wrn > nul

[!Aman!]

I found the problem, when I use all_packages_to_one, the occurrence of such a loss. :confused::confused:

TOOLS\all_packages_to_one > nul
del buildpkg.wrn > nul
which kitchen did u use? Ervius' or Bepe's?

[VJstar]

which kitchen did u use? Ervius' or Bepe's?

bepe's .... help me fixed this. I have already met twice, very confused. This is the first 19972 is 20931

. Never happened before :confused:

[!Aman!]

bepe's .... help me fixed this. I have already met twice, very confused. This is the first 19972 is 20931

. Never happened before :confused:
interesting... i faced this problem at few times with Ervius' kitchen so i started using bepe's where i didnt face this issue. try Ervius' kitchen then, it is surely related to some dsms.

[VJstar]

interesting... i faced this problem at few times with Ervius' kitchen so i started using bepe's where i didnt face this issue. try Ervius' kitchen then, it is surely related to some dsms.

I am grateful that you reply, I await your amendments. In any case, very grateful :D

[VJstar]

I am very sure that the problem here. But how are we to do? Dsm for a unified standard or re-improvement tools all in one? :eek:

PS: I repeated the test more than ten times more than the results obtained :D

[!Aman!]

I am very sure that the problem here. But how are we to do? Dsm for a unified standard or re-improvement tools all in one? :eek:

PS: I repeated the test more than ten times more than the results obtained :D
try Ervius' kitchen without using All_packages_to_one.exe tool or try with empty dsms in the OEM folders.

[VJstar]

try Ervius' kitchen without using All_packages_to_one.exe tool or try with empty dsms in the OEM folders.

yes.. i just do this..i'm done. used bepe's kitchen is same..don't used all in one it's okay. :D

[kokotas]

i've another method for u guys to change the PP. search the 03 15 A0 03 02 15 A0 13 00 10 83 E5 62 C2 FF EB in yours S000 of nk.exe and change the string marked in Red color to 00 00 A0 E1. from there onwards u can simply use the old Multi-platform PP changer.exe (that is also found in kaiser kitchen) to change ur PP on the OS.nb. this should make the kitchen even simpler :D

PS: this method works regardless of the device.
Bro, I think I'm going crazy...
When I did the above change in nk.exe, the results were:
1.The Multi-platform PP changer(tried v2.1 & v2.21) didn't work.It recognized my pp as 2MB eventhough it was 12MB.
2.The ROM that was built with this nk.exe had a very strange behavior:
Available RAM was 118MB(!) and the pp size could not be changed!
Tried to make it (pp size) 0MB & 8MB but the RAM was always 118MB!

Actually, this is cool cause the free RAM was very high too(~97MB!) but I just wonder what the f#$% happened?:D

Regards!

[!Aman!]

Bro, I think I'm going crazy...
When I did the above change in nk.exe, the results were:
1.The Multi-platform PP changer(tried v2.1 & v2.21) didn't work.It recognized my pp as 2MB eventhough it was 12MB.
2.The ROM that was built with this nk.exe had a very strange behavior:
Available RAM was 118MB(!) and the pp size could not be changed!
Tried to make it (pp size) 0MB & 8MB but the RAM was always 118MB!

Actually, this is cool cause the free RAM was very high too(~97MB!) but I just wonder what the f#$% happened?:D

Regards!
that is the expected behaviour :D
after u change that particular HEX string (mentioned in RED), the HEX string (03 15 A0 etc etc) that we have been using till date becomes ineffective and changing the PP at those offsets is useless. PP changer works as it should i.e. 2 MBs PP for Elf as well as Elfin :D. hope its clear now ;)

[kokotas]

that is the expected behaviour :D
after u change that particular HEX string (mentioned in RED), the HEX string (03 15 A0 etc etc) that we have been using till date becomes ineffective and changing the PP at those offsets is useless. PP changer works as it should i.e. 2 MBs PP for Elf as well as Elfin :D. hope its clear now ;)
Thanx for the explanation bro:D
I understand now what's happened!
Very clever!

[!Aman!]

Thanx for the explanation bro:D
I understand now what's happened!
Very clever!
hehe, so i think u can introduce the PP changer in the kitchen at the end of the creation of OS.nb so that users can modify the PP. if people don't want to edit the hex string in the nk.exe, then there is another option. that string can also be edited after os.nb is created, followed by the PP changer ;)

[Demo[95]]

hehe, so i think u can introduce the PP changer in the kitchen at the end of the creation of OS.nb so that users can modify the PP. if people don't want to edit the hex string in the nk.exe, then there is another option. that string can also be edited after os.nb is created, followed by the PP changer ;)

Best idea, i've ever heard :D

[!Aman!]

;2935933']Best idea, i've ever heard :D
hehe, thanks :D.. but its upto the Kitchen owner and also upto the users.

[trueg]

kokotas, is there possibly a problem with Hybrid Kitchen and SD Encryption? I just noticed a few hours ago that all of my ROMs based on 3.10.710.0 had an error in SD Encryption were it would be enabled by default and could not be disabled.

The error existed in my original dump that I did with Hybrid Kitchen. I did a search and there are other Kitchens that had the same problem.

Anybody else have this problem with 1.4.3?

[VJstar]

kokotas, is there possibly a problem with Hybrid Kitchen and SD Encryption? I just noticed a few hours ago that all of my ROMs based on 3.10.710.0 had an error in SD Encryption were it would be enabled by default and could not be disabled.

The error existed in my original dump that I did with Hybrid Kitchen. I did a search and there are other Kitchens that had the same problem.

Anybody else have this problem with 1.4.3?

There is no problem, it's your own mistakes. If you xip in mencfilt.dll and boot_MS.rgu deleted. The result is that you like that. This module is the function. Hybird_kitchen is the default. The first page is described in detail

:D:D

[kokotas]

Ref_XIP_OUT & Ref_XIP folders inside Prepare_XIP are the latest 3.10ROM's XIP, but modified as follows:
-removed modules:
cachefilt.dll, hd.dll, mencfilt.dll, osaxst0.dll
-removed files:
boot_ms.rgu, bmui.nb0
-edited files:
boot.hv, boot.rgu,
REMOVED ENTRIES:
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\Fil ters\CacheFilt]
"Dll"="CacheFilt.dll"
"Order"=dword:2

[-HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\Fil ters\CacheFilt]
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Index"=dword:00000001
"Prefix"="DRM"
"Dll"="lsomacore.dll"
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\L sFilter]
"Order"=dword:00000001
"Dll"="LSFILTER.dll"
[HKEY_LOCAL_MACHINE\Init]
"Launch98"="TimeWizard.exe"
723fb954-d931-4348-b672-82a188e587b5.rgu
REMOVED ENTRIES:
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\E NCFilt]
"EncryptByDefault"=dword:0
-edited modules:
nk.exe
RTC is enabled
-ALL MSXIPKernel modules are relocated to achieve better XIPPorting

If you include LockStreamDRM PACKAGE in your ROM and you use the Ref_XIP as your \ROM\XIP(folder), add the removed (from boot.rgu) entries
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Index"=dword:00000001
"Prefix"="DRM"
"Dll"="lsomacore.dll"
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\L sFilter]
"Order"=dword:00000001
"Dll"="LSFILTER.dll"
[HKEY_LOCAL_MACHINE\Init]
"Launch98"="TimeWizard.exe"
in the PACKAGE's *.rgu.

If you are building your ROM with option 1 you need:
ROM\xip_out.bin ,
ROM\XIP\boot.rgu(ONLY) and
ROM\OS.nb.payload
This option doesn't build the xip_out.bin(buildxip.exe is not used).
You must build your xip_out.bin with XIPPort before starting building OS.
So you should select this option ONLY IF you used option 1 in XIPPorting (or IF you decided to use a dumped ELFIN xip.bin as xip_out.bin and the dumped boot.rgu too).

If you are building your ROM with option 2(or even just run the PkgToolsBuildos-4.3b1) you need:
ROM\XIP(ALL FILES and MODULES) ,
ROM\romhdr.bin and
ROM\OS.nb.payload
This option builds the out.bin(buildxip.exe is used)from the XIP(folder).
You could create your XIP(folder) with dumprom etc..
So you should select this option ONLY IF you used option 2 in XIPPorting (or IF you decided to use a dumped ELFIN XIP(folder)).

Easy(advisable) way to cook is option 2 in XIPPorting & Ervius PkgToolsBuildos! (Don't get confused with the other option)

PP Patching is included in the kitchen operation!
You just set your favorite pp size at the beginning(installing) and each Rom you build is already patched!
If you make the following hex change in nk.exe's S000
i've another method for u guys to change the PP. search the 03 15 A0 03 02 15 A0 13 00 10 83 E5 62 C2 FF EB in yours S000 of nk.exe and change the string marked in Red color to 00 00 A0 E1. from there onwards u can simply use the old Multi-platform PP changer.exe (that is also found in kaiser kitchen) to change ur PP on the OS.nb. this should make the kitchen even simpler

PS: this method works regardless of the device
then the kitchen's PP Patching doesn't work!
You should use the suggested by Aman Multi-platform PP changer v2.21!
Finally, I don't have an ELF to test, but after the above change then I think that the pp size is the same for both ELF&ELFIN(not dynamic).

EDIT:Multi-platform PP changer v2.21 included in the kitchen and reuploaded today..

Regards!

[trueg]

OK, that was a lot of information to take in, but basically my problems arose because I used my dumped XIP.bin as XIP_out.bin. Since the dumped XIP.bin contains all of the SD Encryption crap, it was included in my ROM. It would have been removed had I ran XIPPort.

I'm guessing then that there is a problem cooking SD Encryption since it was corrupted in the dumping/cooking process?

I included LockstreamDRM in my ROM, mostly because it was in the original and I assumed I needed it. I need to add that bit of code to boot.rgu for it to work correctly? Can I just remove it? What does it do?

EDIT: I just checked my boot.rgu and all of the lockstream code is still there, I assume because I am using the dumped boot.rgu.

[trueg]

Could the problem I had with being unable to change sound and notifications and then getting stuck in the application be related to using the default kitchen boot.rgu and LockStreamDRM without adding the LockStreamDRM registry entries to boot.rgu?

[dsixda]

Hey, if you cook a 2.xx ROM with the new 3.xx OS.nb.payload AND with ULDR removed, is it going to work properly after a flash?

Also, I heard that Koko's kitchen has a new payload of only 29MB?? How'd you do that? I am using the OS.nb.payload from the 3.07 Indian WWE, which is over 100MB!

[kokotas]

Could the problem I had with being unable to change sound and notifications and then getting stuck in the application be related to using the default kitchen boot.rgu and LockStreamDRM without adding the LockStreamDRM registry entries to boot.rgu?
Possible!
I think I did tell you to replace the boot.rgu with the dumped one;)
Hey, if you cook a 2.xx ROM with the new 3.xx OS.nb.payload AND with ULDR removed, is it going to work properly after a flash?
Generally speaking,
yes it will work!
I consider the payload as an (elastic) shell in which you "put" your files..
If you cook a ROM with OEMXIPKERNEL from a 2.xx ROM in this kitchen(1.4.3) then it won't work, cause the pp patching will alter the wrong offset and you'll end up with nonbootable device.
UNLESS you edit the bat files in order to target the right offset, so it will be ok!
Also, I heard that Koko's kitchen has a new payload of only 29MB?? How'd you do that? I am using the OS.nb.payload from the 3.07 Indian WWE, which is over 100MB!
I recooked the payload, removed ULDR & reduced the xip available part.
Check change log bro;)

Regards!

[dsixda]

I recooked the payload, removed ULDR & reduced the xip available part.
Check change log bro;)

Regards!

Damn! I didn't see that.. ;)

Also, would you guys say that XIP has a lot to do with memory leaks, or would SYS be more directly responsible (if you ignore OEMs)?

[trueg]

Possible!
I think I did tell you to replace the boot.rgu with the dumped one;)



Exactly, by using the dumped one, all of the LockStreamDRM entries were put back in which corrected the sounds and notification problem.

Currently, I am trying to build a stock 3.10.710.0. I'm using my dumped OEM and SYS and then your Ref_XIP as the XIP. I added the LockStreamDRM registry entries back into boot.rgu and used option 2 (PkgToolsBuildos) to build a ROM which in turn creates out.bin.

I renamed out.bin to xip_out.bin and then ran option 1 to create a ROM for testing.

Everything flashed fine. Changing notifications worked (I assume because LockStreamDRM is working now).

Problem: Encryption under settings is checked! How can this be? I don't believe it is actually working since mencfilt.dll doesn't exist and I don't see a menclog file on my SD card, but the option is checked and can not be unchecked.

[kokotas]

Also, would you guys say that XIP has a lot to do with memory leaks, or would SYS be more directly responsible (if you ignore OEMs)?
That's a good question...
I didn't think of it till now. Well my vote (without being an expert) goes to SYS(&OEM)
cause the files in XIP do not require to be copied into ram before execution..
I hope someone has a more clear view of this:)
Problem: Encryption under settings is checked! How can this be? I don't believe it is actually working since mencfilt.dll doesn't exist and I don't see a menclog file on my SD card, but the option is checked and can not be unchecked.
Since you used the Ref_XIP for XIP then the mencfilt.dll is not present, so this
control panel item is not really working(as you correctly said)!
Just hide it from your Settings and it will be ok:)
Oh! You could also remove DeviceEncryptionPolicy.dll from the Shell folder..
Regards!

[trueg]

Since you used the Ref_XIP for XIP then the mencfilt.dll is not present, so this
control panel item is not really working(as you correctly said)!
Just hide it from your Settings and it will be ok:)
Oh! You could also remove DeviceEncryptionPolicy.dll from the Shell folder..
Regards!

If DeviceEncryptionPolicy is only used for SD Encryption and I'm not using it, I might as well get rid of it. Are there any registry entries tied to it that can also be removed?

Edit: even removing DeviceEncyptionPolicy.dll doesn't fix the fact that Encryption is checked. It's strange because last night when I first realized this encryption problem, all I had to do was delete mencfilt.dll and boot_ms.rgu and then I couldn't enable it. These files are indeed missing from Ref_XIP but it still gets checked. As long as it is not working, I guess I will just hide the control panel and assume I am safe.

[kokotas]

If DeviceEncryptionPolicy is only used for SD Encryption and I'm not using it, I might as well get rid of it. Are there any registry entries tied to it that can also be removed?
There are some reg_entries in SYS that should be removed too, but I don't remember which *.rgu...
Well, search your SYS *.rgus and when you see something like:
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\E NCFilt]
remove it.
Edit: Try Shell,BaseApps,OS

Edit: even removing DeviceEncyptionPolicy.dll doesn't fix the fact that Encryption is checked. It's strange because last night when I first realized this encryption problem, all I had to do was delete mencfilt.dll and boot_ms.rgu and then I couldn't enable it. These files are indeed missing from Ref_XIP but it still gets checked. As long as it is not working, I guess I will just hide the control panel and assume I am safe.
As long as it is not working, you are "safe".

Happy Cooking;)!

[trueg]

How about this one?

[HKEY_LOCAL_MACHINE\Comm\Security\SDP\BootFunctions \DeviceEncryptionPolicy]
"Dll"="MencFilt.dll"
"DllEntryPoint"="LoadEncryptionPolicy"
"Order"=dword:20000

Note: both this and the entry you mention are in \OS\*.rgu

[kokotas]

How about this one?

[HKEY_LOCAL_MACHINE\Comm\Security\SDP\BootFunctions \DeviceEncryptionPolicy]
"Dll"="MencFilt.dll"
"DllEntryPoint"="LoadEncryptionPolicy"
"Order"=dword:20000
Yes!
You got it!
You removed the file=>time to clean up your Registry too:D

[humrod]

Hi kokotas. I'm learning about your kitchen. I port a coredll.dll and it updated suscesfully, but appear a message: run createxip.exe and insert.exe.
The question is: i cant localize the createxip.exe.
the insert.exe is in tools folder.

[Ameet]

Could the problem I had with being unable to change sound and notifications and then getting stuck in the application be related to using the default kitchen boot.rgu and LockStreamDRM without adding the LockStreamDRM registry entries to boot.rgu?
Actually this problem is mostly related to the physical ringtone present in the ROM. If you have removed the Ring_Windows (or something) .wma file then you get stuck in the Sound & Notifications tab and not able to change the sounds

Sorry if this is already answered

[trueg]

If DeviceEncryptionPolicy is only used for SD Encryption and I'm not using it, I might as well get rid of it. Are there any registry entries tied to it that can also be removed?

Edit: even removing DeviceEncyptionPolicy.dll doesn't fix the fact that Encryption is checked. It's strange because last night when I first realized this encryption problem, all I had to do was delete mencfilt.dll and boot_ms.rgu and then I couldn't enable it. These files are indeed missing from Ref_XIP but it still gets checked. As long as it is not working, I guess I will just hide the control panel and assume I am safe.

I wanted to find out why Encryption gets checked when I use the Ref_XIP and not when I use my dumped one with mencfilt.dll and boot_ms.rgu deleted. The key is...

723fb954-d931-4348-b672-82a188e587b5.rgu
REMOVED ENTRIES:
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\E NCFilt]
"EncryptByDefault"=dword:0

Once you delete this from the registry, Encryption gets checked and can not be unchecked. If mencfilt.dll is deleted, then it doesn't really matter, but I was glad to understand why this was happening.

[trueg]

Actually this problem is mostly related to the physical ringtone present in the ROM. If you have removed the Ring_Windows (or something) .wma file then you get stuck in the Sound & Notifications tab and not able to change the sounds

Sorry if this is already answered

In my case, no ringtones were deleted. It can be re-created easily. Simply remove the LockStreamDRM registry entries from boot.rgu and include LockStreamDRM in your ROM and you will run into a situation where it 'locks' up when you enter sounds & notifications. Either don't include LockStreamDRM in your OEM or ensure the registry entries are included in boot.rgu.

[kokotas]

If anyone is interested in trying something for me, here you go:
Hybrid Kitchen v2.0.0 (http://forum.xda-developers.com/showpost.php?p=2326150&postcount=2)
Let me know if you find this setup more fast-easy2use than the previous..

Regards!

[VJstar]

I do not want to put it on the C disk, would like to put any letter, how do I do? :D

I changed the path of all but it's not working... :confused:

Can not be in the running for the first time on the path to personalized settings? :D

[kwbr]

If anyone is interested in trying something for me, here you go:
Hybrid Kitchen v2.0.0 (http://forum.xda-developers.com/showpost.php?p=2326150&postcount=2)
Let me know if you find this setup more fast-easy2use than the previous..

Regards!
Hi Kokotas, what has changed in the new version?

[kokotas]

I do not want to put it on the C disk, would like to put any letter, how do I do? :D

I changed the path of all but it's not working... :confused:

Can not be in the running for the first time on the path to personalized settings? :D
The requirement for the kitchen to work is to "install" it directly to the drive where your windows are installed(systemdrive).
If your windows are in D drive , then place the kitchen in D drive.
If your windows are in E drive , then place the kitchen in E drive.
...
If you want to put it in another drive(not where your OS is)you have to edit EVERY batch file(including First_Run_For_ELF(in)_Hybrid_Kitchen.bat)&replace %systemdrive% with the drive's letter.
Hi Kokotas, what has changed in the new version?
Regarding the cooking process,the only change is that I included the autopather by cmonex for the removal of sign/cert checking.
But I changed a lot the structure&the access of the kitchen!
Check changelog too.

Regards!

[jonbus]

Hi everybody, i have a little "issue" here...

I build a rom using this wonderful Kitchen, and i wnated to update it and i took the generated nbh and try to dump it but it doesn´t create OEM ans SYS folders....neither this kitchen or any other or the PKGTool by itself....

Why could be that? any solution? unfortunately i did not save the base OEM and SYS folders....

Thanks in advance

[trueg]

If you cook using Bepe's BuildOS the resulting ROM will not be dumpable. You need to cook with Ervius PkgToolsBuildOS in order to have a dumpable ROM.

[jonbus]

If you cook using Bepe's BuildOS the resulting ROM will not be dumpable. You need to cook with Ervius PkgToolsBuildOS in order to have a dumpable ROM.

that´s what i suspected....

Thanx Trueg!

[chihliouma]

If you cook using Bepe's BuildOS the resulting ROM will not be dumpable. You need to cook with Ervius PkgToolsBuildOS in order to have a dumpable ROM.

I see. but what I am wondering if there is any other tool than PKGTOOLS that can be used to dump ROM cook by using Bepe's BuildOS ? Thanks.

[trueg]

I see. but what I am wondering if there is any other tool than PKGTOOLS that can be used to dump ROM cook by using Bepe's BuildOS ? Thanks.

No I don't believe so. The information needed to separate the packages is simply not included in the final ROM when built with bepe's BuildOS.

[jonbus]

No I don't believe so. The information needed to separate the packages is simply not included in the final ROM when built with bepe's BuildOS.

Well that´s strange, very strange....if i use Hypercore Kitchen, it uses Bepe´s BuilOs, i can dump the nbh....why´s that?? Hypercore doesn´t use Greloc, could be that?...

Another thing about Hybrid Kitchen 2.0.1, don´t know if it´s only in my PC:

The option "2" Build ROM - Using Ervius PkgToolsBuildos, in Build Rom ( "c" from main menu) doesn´t work for me, it just send me back to main menu...

Checking the BuildNB.bat, i realize that there is an "&" in "PkgTools&BuildOS.exe", maybe my PC do not recognize that character...just took it off and renamed the program in ELF(in)_Hybrid_Kitchen\Build_ROM as well...and worked!...I also modify a little that batch, just a little more "interactive", resulting in this:
@echo off
SET ALL=1
:st
echo.
echo. Starting building section...
echo. Autofixing and Autorelocating SYS is "enabled"!
echo.
echo. Select your option and press ENTER
echo.
echo. [1] - Build (Protected) ROM
echo. Requires: ROM\xip_out.bin ,
echo. ROM\XIP\boot.rgu(ONLY) and
echo. ROM\OS.nb.payload
echo. [2] - Build ROM - Using Ervius PkgToolsBuildos
echo. Requires: ROM\XIP(ALL FILES and MODULES) ,
echo. ROM\romhdr.bin and
echo. ROM\OS.nb.payload
echo. [3] - Return to Main Menu
echo. [0] - Exit
echo.
echo.
Set /P Choice=Choice :
IF '%Choice%'=='1' GOTO :1
IF '%Choice%'=='2' GOTO :2
IF '%Choice%'=='3' GOTO :main
IF '%Choice%'=='0' GOTO :end
set choice=

:main
cls
echo.
set choice=
cd %systemdrive%\ELF(in)_Hybrid_Kitchen\Batch
Start_Kitchen.bat

:1
cls
cd %systemdrive%\ELF(in)_Hybrid_Kitchen\Build_ROM\ROM \XIP
if exist "nk.exe" ( echo.Rearranging files inside ROM folder...
attrib boot.rgu -r -s -h -a
cd ..
ren "XIP" "NULL" > nul
mkdir XIP > nul
copy "NULL\boot.rgu" "XIP\" > nul
ren romhdr.bin romhdr )
if not exist "boot.rgu" ( echo.Place ONLY boot.rgu inside XIP folder!
goto :xipfolder1 )
cd %systemdrive%\ELF(in)_Hybrid_Kitchen\Build_ROM\ROM \XIP
cd %systemdrive%\ELF(in)_Hybrid_Kitchen\Build_ROM
echo.
echo.Creating 'dump' folder...
echo.
echo.
TOOLS\BuildOS.exe -auto
echo.
echo.Done!

REM ================================================== =========================================
echo.
echo.Relocating modules in 'dump' folder...
echo.
echo.
TOOLS\G'Reloc.exe -doit -dump
echo.
echo.Done!

REM ================================================== =========================================
echo.
cd %systemdrive%\ELF(in)_Hybrid_Kitchen\Batch
CALL CreateROM.bat

pause
goto :EOF

:2
cd %systemdrive%\ELF(in)_Hybrid_Kitchen\Build_ROM\ROM \XIP
if not exist "nk.exe" ( echo.XIP folder is empty!
goto :xipfolder2 )
cd %systemdrive%\ELF(in)_Hybrid_Kitchen\Build_ROM\ROM
if exist romhdr ( ren romhdr romhdr.bin ) > nul
if not exist romhdr.bin ( echo.romhdr.bin is missing from ROM folder!
goto :romfolder )
if not exist OS.nb.payload ( echo.OS.nb.payload is missing from ROM folder!
goto :romfolder )
cd %systemdrive%\ELF(in)_Hybrid_Kitchen\Build_ROM\ROM \XIP
cd %systemdrive%\ELF(in)_Hybrid_Kitchen\Build_ROM\
PkgToolsBuildOS.exe
GOTO :main

:error
echo.
echo. ERROR! (errorlevel: %errorlevel%)
pause

:end
set choice=
exit

:xipfolder1
"%systemroot%\explorer" %systemdrive%\ELF(in)_Hybrid_Kitchen\Build_ROM\ROM \XIP
pause
goto :1

:xipfolder2
"%systemroot%\explorer" %systemdrive%\ELF(in)_Hybrid_Kitchen\Build_ROM\ROM \XIP
pause
goto :2

:romfolder
"%systemroot%\explorer" %systemdrive%\ELF(in)_Hybrid_Kitchen\Build_ROM\ROM
pause
goto :st

I repeat, i don´t know if that is happening in all PC, dont know if it MY configuration that Windows do not recognize "&" as a character...

Hope i can help!


.

[trueg]

Well that´s strange, very strange....if i use Hypercore Kitchen, it uses Bepe´s BuilOs, i can dump the nbh....why´s that?? Hypercore doesn´t use Greloc, could be that?...

I don't know, I haven't used Hypercore in a long time. I just know that using option 1 in Hybrid Kitchen creates a ROM that can not be dumped (and have the packages separated into OEM & SYS). Option 2 seems to work fine for me. ROMs made with option 2 dump fine for me. They are also a few MB larger.

[!Aman!]

Bepe's kitchen is based on all_packages_to_one.exe, which removes all the rgu's, dsm's etc from the ROM and thus makes it undumpable :)
hypercore doesn't work on that principle.

[kokotas]

Another thing about Hybrid Kitchen 2.0.1, don´t know if it´s only in my PC:

The option "2" Build ROM - Using Ervius PkgToolsBuildos, in Build Rom ( "c" from main menu) doesn´t work for me, it just send me back to main menu...

Checking the BuildNB.bat, i realize that there is an "&" in "PkgTools&BuildOS.exe", maybe my PC do not recognize that character...just took it off and renamed the program in ELF(in)_Hybrid_Kitchen\Build_ROM as well...and worked!...
Sorry for that one!When I realized that I forgot that "&" in the batch, I reuploaded the kitchen!
I also modify a little that batch, just a little more "interactive", resulting in this:
...
I repeat, i don´t know if that is happening in all PC, dont know if it MY configuration that Windows do not recognize "&" as a character...

I just wasn't fast enough...but it's good that you found that mistake&corrected it by yourself!
Regards!

[jonbus]

Bepe's kitchen is based on all_packages_to_one.exe, which removes all the rgu's, dsm's etc from the ROM and thus makes it undumpable :)
hypercore doesn't work on that principle.
Thanx Htctouchp! but when does it stores the registry? in the hives (default and user)?

Sorry for that one!When I realized that I forgot that "&" in the batch, I reuploaded the kitchen!

I just wasn't fast enough...but it's good that you found that mistake&corrected it by yourself!
Regards!
Ok Kokotas! thank you....

One more thing, may i have your permission to translate your kitchen to spanish? and use it in a cooking tutorial i´m planning to do?

Thanx Master!

[kokotas]

Thanx Htctouchp! but when does it stores the registry? in the hives (default and user)?


Ok Kokotas! thank you....

One more thing, may i have your permission to translate your kitchen to spanish? and use it in a cooking tutorial i´m planning to do?

Thanx Master!
Hi jonbus!
You're correct! The registry settings are "stored" in the hives (rgucomp builds the *.hv from all the *.rgus) .
This is free to use or edit but at your own risk...
so go ahead and make this kitchen in spanish.It's not that I have a copyright or something:Dhehehe:D

Regards!

[aflika]

Please help
Rom edit problems

http://img124.imageshack.us/img124/6740/adszon9largejc5.png (http://imageshack.us)
http://img124.imageshack.us/img124/adszon9largejc5.png/1/w896.png (http://g.imageshack.us/img124/adszon9largejc5.png/1/)

Help please! :(:(:(

[kokotas]

Hey man!
I can't understand what the error is about, but if you follow the instructions in 1st post then there shouldn't be a problem!
Plus have in mind that this is a WWE kitchen tested on WWE Windows.

Regards!

[aflika]

Hey man!
I can't understand what the error is about, but if you follow the instructions in 1st post then there shouldn't be a problem!
Plus have in mind that this is a WWE kitchen tested on WWE Windows.

Regards!

thanks... I'm sorry I'm bad english

[trueg]

Hi jonbus!
You're correct! The registry settings are "stored" in the hives (rgucomp builds the *.hv from all the *.rgus) .

Is this automatic when using Bepe's BuildOS? I just starting using Raphael ROM Kitchen and even when using what appears to be Bepe's BuildOS I get all of my OEM rgus in my Windows folder. Would that kitchen need to use rgucomp in order to get the same results as option 1 in your kitchen?

[Demo[95]]

Is this automatic when using Bepe's BuildOS? I just starting using Raphael ROM Kitchen and even when using what appears to be Bepe's BuildOS I get all of my OEM rgus in my Windows folder. Would that kitchen need to use rgucomp in order to get the same results as option 1 in your kitchen?

I think it's TOOLS\all_packages_to_one.exe that produce this behavior.

Kind regards.

[lokura]

It is embarrassing how easy it is :o , a verry good job
thanks for your kitchen, i finally have my own rom cooked and working in my elfin
really a few changes, (removed sqm and .net 2, and added .net 3.5, remote tracker and security_off) but is a good begin for me
the pity is that infamous butterfinger efect on lattest oficial roms, any chance to solve this?

[kokotas]

v2.0.7 @ 1st post is up!
New version. Less confusing. Probably the Final.
Cause there is something new and better ;) ...
================================================== ====================================
If anyone is interested here (http://forum.xda-developers.com/showpost.php?p=2763120&postcount=4) it is. Mostly as an example!

Regards!

[aflika]

thank you kokotas