Hi Everybody, I have a good news, Ervius Visual Kitchen V 1.8.1 is working well on GENE.
Thanks to:
- Ervius & Bepe for the great tools and kitchen
- Olipro
- tadzio
- +Que PPC for the Reference Tutorial
Download Link KITCHEN TOOL Only:
EXE: http://www.4shared.com/file/127636364/a3ff9677/Ervius_Kitchen_For_GENE_by_BesFen.html
RAR: http://www.4shared.com/file/127785396/6450a6ce/Ervius_Kitchen_For_GENE_by_BesFen.html
Download Link 21844 KITCHEN:
http://www.4shared.com/file/127886874/fb6b18b6/21844_Ervius_Kitchen_For_GENE_by_BesFen.html
INSTALLING "ERVIUS VISUAL KITCHEN" ===> If you download Kitchen tools only
1. Download the Kitchen tools, and extract it.
2. run "Erviuskitchen.exe", it will give error, just click OK until the window appear.
3. Prepare your Base Working ROM and Unprotected, I suggest you can use Krazy 21051 ROM, put it in the folder and name it "Base ROM", only this ROM in the folder.
4. Click "Dump nbh/nb/payload", and navigate to the Base ROM, a window will appear during process, just click OK and wait until finish.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It will make folder dump inside folder Base ROM, and that is your kitchen for 21054. By extracting it we have: XIP, os.nb.payload, romhdr.bin that will be use to create all ROM.
Note: If you dump Old GENE, it will work only for OLD GENE, and either for NEW GENE. the different only in XIP. You can replace the xip for it.
CONTENT OF 21844 KITCHEN
This is the kitchen root preview in Windows Explorer:
1. EXT Folder
The External packages (EXT) folder is divided into Device Specific folders and a Shared folder:
*Device Specific folders are typically used for files (packages) that should only be applied to a specific type of the device.
Each Device Specific folder is further divided into Operating System Build Version Specific folders and a Common folder.
*Operating System Build Version Specific folders are typically used for files (packages) that should only be applied to a specific build (version) of Operating System. The Common folder is typically used for files (packages) that can be installed on any Operating System build version.
2. OEM Folder
The OEM folder can contain multiple Device Specific folders.
*Each Device Specific folder is further divided into Locale Specific folders and a Common folder.
*The Common folder is typically used for files (packages) that can be installed in any locale – not specific to a language.
*Locale Specific folders are typically used for files (packages) that should only be applied to a specific locale.
3. ROM Folder
The ROM folder is divided into Device Specific folders and a Shared folder.
*The Shared folder is typically used for kernel system files that are compatible amongst devices. (MSXIPKERNEL folder)
*Device Specific folders are typically used for kernel system files that should only be applied to a specific type of the device. (OEMXIPKERNEL folder)
-The Shared folder is further divided into Operating System Build Version Specific folders. Operating System Build Version Specific folders are typically used for kernel system files that should only be applied to a specific build (version) of Operating System.
-Each Device Specific folder is further divided into Operating System Build Version Specific folders.
4. SYS Folder
The system (SYS) folder is divided into Operating System Build Version Specific folders.
*The Build Version Specific folders will often contain files (packages) specific to the device DPI (Dot Per Inch) and Horizontal/Vertical display size.
*Each Operating System Build Version Specific folder is further divided into a ROM DPI, ROM Resolution, and Shared folder – providing a significant amount of flexibility during ROM compilation.
*The ROM DPI, ROM Resolution, and Shared folders are further divided into Locale Specific folders and a Common folder.
*The Common folder is typically used for system files (packages) that can be installed in any locale – not specific to a language.
*Locale Specific folders are typically used for system files (packages) that should only be applied to a specific locale – for example, 0409 (English).
Updating visual kitchen with new build
UPDATING VISUAL KITCHEN WITH NEW BUILD
We assume to update my 21844 visual kitchen for OLD GENE with newer Build (example 23034).
A. EXT
1. In the EXT\OLDGENE create a new empty folder with the name of the build (example 23034).
2. copy the folder “OLDGENE_External_Packages” inside EXT\OLDGENE\21844 to EXT\OLDGENE\23034.
Now you extended packages is ready
B. OEM
No need to modify this Folder
C. ROM
1. In the ROM\ OLDGENE Folder, create a new folder with the name of the build (example 23034). Copy the OEMXipKernel folder from ROM\ OLDGENE \21844 into this folder as shown below:
2. in the ROM\Shared Folder, create a new folder with the name of the build (example 23034). Copy the MSXipKernel folder from New Build into this folder as shown above.
D. SYS
In the SYS Folder, create a new folder with the name of the build (example 23034). Copy the SYS from the new Build into this folder as shown below:
Now your NEW BUILD KITCHEN IS READY
DUMP XIP.BIN TO GET MSXIPKernel
TO make a new build ROM, we need MSXIPKernel, and sometime people only provide xip.bin of the new build.If it happens we need to dump it to get MSXIPKernel, download that file, and dump it with XIPPort.exe, here is the tools.:
http://www.4shared.com/file/125449740/a1b9e454/XIPPort.html
Now, put the attached file and the xip.bin in the same folder, then run XIPPort.exe, click “dump xip.bin” and wait until folder “OUT” appear, then click “make pkgs”, close the XIPPort.exe.
Go to folder “out” and you will find “Files and Modules” folder, inside each folder, you will find folder MSXIPKernel. Move the module inside OUT\MODULES\MSXIPKernel to OUT\FILES\MSXIPKernel, now you have the MSXIPKernel. And don’t forget to delete any *.txt file inside MSXIPKernel.
Using visual kitchen
USING VISUAL KITCHEN
After add new build, run the kitchen, and you will get pic as below:
1. Choose your device, NEW GENE or OLD GENE
2. Choose your XIP Build
3. Choose your SYS Build
4. Choose your EXT Build
The default compression is XPR, you can make LZX compression by select the LZX.
You can change the PP, click "Other" Buton, you will see pic below:
Enter the number of PP as you want.
* I disable the ULDR, Imgstart address, and nocert, this feature are not working for GENE.
* You can weather the package in the EXT, OEM, or SYS to include in the ROM or no by double click the name of packages.
OK that is all, you ready to click the "Create ROM" Button.
HAPPY COOKING Time to SLEEP....
Great News
well done bro.....
gr8 news man.
waiting 4 further explanation
very thanks besfen
Thats really great will try it soon, thanks Besfen, our Best Friend
Its BesFen always who changes Gene Upgrading forum!
Please ...... Someone upload it as zip or rar.
Xumit said:
Please ...... Someone upload it as zip or rar.
Click to expand...
Click to collapse
Link update in the 1st post, add RAR format
You are the real KITCHEN KING, Thanks a lot.
Thats really great
Thats really great will try it soon.
I am new comer here to this forum. But felt more comfortable and enjoyed in this forum.
Thanks to all...
...Karan999, BesFen, krazy_about_technology, deathgame, etc many credits to them.
Currently using: Self cooked ROM from Besfen's Kitchen 23017 on Gene
LOL who made this thread sticky, even it's incomplete BTW waiting for next part .
Thank you,,I'll try this ASAP...
This tool is not only for WM6.5 right? Can also for WM6.1?
ankit360 said:
LOL who made this thread sticky, even it's incomplete BTW waiting for next part .
Click to expand...
Click to collapse
Why did you say incompatible? I build my 21844 ROM with it and it work great, XPR or LZX compression work, PP change also work. The feature that aren't work only udrl & imgsf start address, GENE don't have UDLR partition.
The only thing you must do are put the right file in the right place.
If you want, I can upload my 21844 kitchen.
BesFen said:
If you want, I can upload my 21844 kitchen.
Click to expand...
Click to collapse
Good idea
BTW I requested the stickey, and Dave obliged
Hi Besfen, thanks for the great contribution.
Thanks for the kitchen Besfen (BEStFriENd)
BesFen said:
Why did you say incompatible? I build my 21844 ROM with it and it work great, XPR or LZX compression work, PP change also work. The feature that aren't work only udrl & imgsf start address, GENE don't have UDLR partition.
The only thing you must do are put the right file in the right place.
If you want, I can upload my 21844 kitchen.
Click to expand...
Click to collapse
LOL i read To be Continued.......... so i think your kitchen is not ready BTW downloading now
Related
Warning to those who don't know what you're doing. Don't to be tempted to attempt this program.
[Introduction]
aChef is a ROM Utility for Hermes and Trinity to convert from OS.nb to imgfs_raw_data.bin and vice versa. (Just like prepare_imgfs.exe and make_imgfs.exe) Then you can use AddFile.exe and DelFile.exe to cook your own ROM.
[Attention]
Currently, this program ONLY designed and tested for supported ROMs (The program will detect automatically). IMGFS generated by the -force option is not tested for the flashing process.
[Usage]
You have to install Java (http://jave.sun.com) to use this program.
To extract to imgfs
==============
java -jar aChef.jar -1 06_OS.nb
To force extract of untested OS to imgfs
==========================================
java -jar aChef.jar -1 06_OS.nb -force
To convert imgfs to 06_OS.nb
=======================
java -jar aChef.jar -2 06_OS.nb
[Change Log]
<0.2.1> (latest)
- fix a bug occurs after delete large files
<0.2.0>
- improve conversion speed
- add support to Trinity OS.nb
- add checking for supported OS.nb
- bug fixes
<0.1.0>
- initial release
[Example]
- Get RUU_signed.nbh from the ROM
C:\test>NBHextract.exe RUU_signed.nbh
C:\test>java -jar aChef.jar -1 06_OS.nb
C:\test>echo 111 > test.txt
C:\test>AddFile.exe test.txt
C:\test>java -jar aChef.jar -2 06_OS.nb
- Flash using Bootloader 1.01 MFG (http://forum.xda-developers.com/showthread.php?t=290206)
Please make sure you know what u are doing before your flash the modified ROM to your device. Do it at ur own risk!!!
woowoo! great work, i'll try it later.
thank y man!
Hi
The tool works.But it needs an actual Java runtime to work.
Just tried it and it seems to work.
Don't know nothing about cooking yet, but it seems okay
Tried it without adding something and the new file is exactly the same as the original
When adding a file it is a little different, from the look of it it seems to work, but who is willing to try a flash?
trion said:
When adding a file it is a little different, from the look of it it seems to work, but who is willing to try a flash?
Click to expand...
Click to collapse
I have tried the flashing part for several times already. After add files of 3xxkb and delete a few files, all the changes were exactly what I expected after the flash.
Whith Hermes RUU_Hermes_HTC_WWE_2.05.xxxx Rom - OK!!!!
But... with Trinity ROMs and old Hermes Roms - Problems!!!
I used your tools for nb-file:
C:\java -jar aChef.jar -1 06_OS.nb
C:\java -jar aChef.jar -2 06_OS.nb
.....after that i got nb file, then I compared this file and original 06_OS.nb. So got many diffrerences between its. Just see my screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lvsw said:
Whith Hermes RUU_Hermes_HTC_WWE_2.05.xxxx Rom - OK!!!!
But... with Trinity ROMs and old Hermes Roms - Problems!!!
Click to expand...
Click to collapse
He also said to only use it on the 2.05 rom.
But I don't see this as a problem, it's just his first alpha release, so we can start experimenting with cooking. It's just that I never done it before and I don't want to brick my device by flashing a failed cooked rom
Maybe someone more experienced in cooking can make a nice AKA 3.x rom that works better than this test version or even a crossbow version would be possible now
can i convert the raw file part of extracted rom in nb flash file?
5n0rk said:
can i convert the raw file part of extracted rom in nb flash file?
Click to expand...
Click to collapse
This will be possible in future release.
lvsw said:
Whith Hermes RUU_Hermes_HTC_WWE_2.05.xxxx Rom - OK!!!!
But... with Trinity ROMs and old Hermes Roms - Problems!!!
.....after that i got nb file, then I compared this file and original 06_OS.nb. So got many diffrerences between its. Just see my screenshot
Click to expand...
Click to collapse
It should work with the newly released version 0.2.0
aChef version 0.2.1 is released to fix a bug...
ahlok_hk said:
aChef version 0.2.1 is released to fix a bug...
Click to expand...
Click to collapse
Thanks! I create firth custom ROM for Trinity! - http://forum.xda-developers.com/showthread.php?p=1141089#post1141089
Does this mean that we can start building ROM's for the TyTN from scratch? Or can we only modify existing ones?
If it is the first case then where can I find all files needed to build my own custom ROM and if anyone knows where to find a nice tutorial I would even be more happy. ;-)
Hi,
I am new to this stuff. How can we try this to convert extended rom file like 04_ExtROM.nb. Once its converted to bin how can we open it.
Thanks.
JohanDC said:
Does this mean that we can start building ROM's for the TyTN from scratch? Or can we only modify existing ones?
If it is the first case then where can I find all files needed to build my own custom ROM and if anyone knows where to find a nice tutorial I would even be more happy. ;-)
Click to expand...
Click to collapse
A tutorial would be perfect. I have lots of things in mind but just to afraid to brick my device.
With his tool it should be possible to update the 2.05 rom with 2.06 stuff from cingular, withouth the cingular crap. And maybe some new stuf from a crossbow rom i guess? and the widcomm stack into the rom
Maybe someone who know how to do this can write a simple tutorial, or point us to one. Or maybe Lvsw is willing to make one for us?
Some things I like to know is, how do you select the folder a file is placed in with addfile and how do you add the registry settings. I guess when you know this it's just adding the stuff you like and that's it..?
trion said:
...
Some things I like to know is, how do you select the folder a file is placed in with addfile and how do you add the registry settings. I guess when you know this it's just adding the stuff you like and that's it..?
Click to expand...
Click to collapse
You can follow the example in post #1 to add and delete file in existing rom. All file will be placed in /windows folder.
Maybe also modify (delete then add) the following files
- modify initflashfiles.dat (cut first 2 bytes after edit with notepad)
- modify default.hv and user.hv
See also this thread for more information: http://forum.xda-developers.com/showthread.php?t=249836
ahlok_hk said:
You can follow the example in post #1 to add and delete file in existing rom. All file will be placed in /windows folder.
Maybe also modify (delete then add) the following files
- modify initflashfiles.dat (remove first 2 bytes edit with notepad)
- modify default.hv and user.hv
See also this thread for more information: http://forum.xda-developers.com/showthread.php?t=249836
Click to expand...
Click to collapse
Thanx, when I have more time I should be able to use this to create a rom with the Widcomm stack in it
And some crossbow stuff. (I'm guessing I can delete the programs and replace them with the programs from any crossbow rom? But when I replace the core windows files I guess I get into trouble?)
Is there a way to test the rom is okay? Or is there always the risk of creating trashed NAND?
why there is no one cook a hermes rom?
i just want to know how many files we can add to the os.nb and the size?(Max ?Mb for all files and Max ?Mb for a single file)
i am chinese and i need to add a font about 4Mb and wince.nls 1M, is it possible?
trion said:
Is there a way to test the rom is okay? Or is there always the risk of creating trashed NAND?
Click to expand...
Click to collapse
I would say that as long as you just modify the imgfs, the generated OS.nb would be safe to flash to NAND. There was an incidence that the aChef had a bug which created an almost empty IMGFS and I flashed it to my Hermes. But it was easily recovered by just flashing another valid OS.nb back to the device.
Of coz I cannot guarantee that it is 100% safe. But the main point of flashing a ROM is:
- type carefully
- use reliable USB cable(don't use retartable one!)
- reboot the PC before flashing.
- reboot the Hermes before flashing.
- make sure battery is 50% or above
- don't touch anything when flashing.
ahlok_hk said:
I would say that as long as you just modify the imgfs, the generated OS.nb would be safe to flash to NAND. There was an incidence that the aChef had a bug which created an almost empty IMGFS and I flashed it to my Hermes. But it was easily recovered by just flashing another valid OS.nb back to the device.
Of coz I cannot guarantee that it is 100% safe. But the main point of flashing a ROM is:
- type carefully
- use reliable USB cable(don't use retartable one!)
- reboot the PC before flashing.
- reboot the Hermes before flashing.
- make sure battery is 50% or above
- don't touch anything when flashing.
Click to expand...
Click to collapse
Thanx!
When I have the time I will start some experiments, unless someone else already created the perfect rom by then
Thanx a lot for your program and the info!
The use of the Rom Kitchen is at your own risk!
Note: This is NOT for beginners, you need to have a good understanding of flashing G3/G4 prophets
This is NOT for answering or asking basic info, use the wiki/search for that.
Rom Kitchen Installation:
Download and install MS .NET framework 2 first
Extract the file ‘Prophet_WM6_RK_S-Core.rar’ anywhere.
The Folder structure will look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Extract ‘FlashOS.zip’ and ‘rgu-hv.zip’ anywhere.
Using the Rom Kitchen in Steps:
STEP (0): Making an OEM Package:(optional, more later)
This step is not necessary at beginning, unless you want to include new OEM Package in the OEM dir of Kitchen.
STEP(1): Run BuildOS.exe:
it will look like this:
Here you can select / de-select any packages you require.
Make sure you don't select too many or it will overflow the rom and you will get any error in the CreateRom.bat step.
Click the green button when you are done and it will create the OS dump.
If you get errors during this, it is probably due to duplicate files/modules in SYS and OEM dirs or due to bad registry entries.
If they occur, it has to be fixed by deleting duplicate files/modules (make sure you know what you are deleting) and correcting the registry (its hard to track registry errors, only change one package at a time).
If there are no errors BuildOS.exe will finish and prompt ‘Done’.
The temp dir will have dump,boot.hv,boot.rgu and log.txt
Do not delete any content at this point.
STEP(2) (a): Editing default/User .hv files:
This can be skipped, but all depends upon need.
This is needed for example when you need to ‘remove’ some reg entries.
For example see:
The base rom used in this kitchen is from the wizard, so we probably need this type of removal again.
To do it , copy default.hv and user.hv( user may not need both) files from dump created above to rgu-hv folder.
Run respective batch file to convert them in *.rgu files and rename *.rgu files to *.txt
edit *.txt files in notepad.
Remember these points:
--------(i)Turn off Word Wrap in notepad
--------(ii)1st line is blank line, type “REGEDIT4”(without quotes)on this line
--------(iii)Make sure last line is blank line
--------(iv)Files should be saved as Unicode not ANSI after editing
--------(v)HKCR & HKLM falls in default.rgu
--------(vi)HKCU and HKU falls in user.rgu
When saving *.txt files in notepad,
--------Select Encoding as Unicode
--------Select file type ‘all’
--------Rename as *.rgu
Now run respective batch file to convert *.rgu file back to *.hv files. Original *.hv files present in rgu-hv dir will be replaced by newly edited *.hv files.
Move new *.hv files back to dump folder in temp dir.
STEP(2) (b): Editing main initflashfiles.dat, why ? (Coming soon)
STEP(3): Run CreateRom.bat:
This batch file uses the dump dir., boot.hv and boot.rgu files to create the OS.nb file.
If there are no errors, the newly created OS.nb is placed in the temp dir.
STEP(4): Flashing the OS:
- Downgrade to AKU 2.2 first (wm5)
- Move your new OS.nb from the temp dir to the FlashOS dir and run UpgradeRom.bat
Screenshots:
Downloads:
PROPHET_WM6_RK_S-CORE
View attachment FlashOS.zip
View attachment rgu-hv.zip
View attachment Guide.zip
Updates:
#1 - 10/06/2007 Reduce imgfs size and put in more OEM/Files
(1)View attachment TOOLS+CreateROM.zip
Extract Zip and replace TOOLS dir and CreateROM.bat with old one in RK.
Modified File/TOOLS are optional, one can continue to work with old ones.
Info on Update #1
- Modified File/Tools repack imgfs block and hence OS.nb to reduced size!!
- Standard size of Shiped OS/Old cutom cook OS is 58368 KB(59,768,832 Byte)
- With the modified File/Tools new OS.nb can be less then 50 MB!!
- Hence its possible to include more OEM Packs and files untill the limit of 58368 KB
- Less imgfs blocks will not increase Storage.
- If OEM Packs/Files are deleted, initflashfile.dat must be edited, if not it will not boot properly
- Flashing reduced size OS.nb with FlashOS, may not prompt completion, so one has to wait as long as to approx 30 min or above to make it complete in hidden mode.
- If you add too many OEM/Files to the OS.nb greater than standard size without any error, but avoid such OS and dont risk ur device by flashing over size OS.nb
- experience with reduced size OS.nb - device switches off frequently after waking up, no other issue found yet.
Credits:
Mamaich,bepe and faria for base framework
Anichillus for base rom Core 2.n
Double_ofour for linux support
Zeusin/Smart1 for explaning ModelID
itsme and Tadzio for his tools
funman for the manual
And many others.........
Hi Nandlal,
Finally after a long wait... Am downloading it now, and will try it out asap. it looks grt and easy to use from what i can see. Thanks a lot for this, and hopefully we will have more custom stable roms coming out based on this RK
PS: SMART1 helped in figuring out the model ID.....so thanks to him
dmc3 said:
can this be use with smart1's???
Click to expand...
Click to collapse
its complete kitchen, u dont need any other rom to use with.
Kitchen uses anichillus's Core 2.n as base rom.
If u just use kitchen with all steps u will get a rom which looks as in post.
P4k1t0 said:
i forget to install it... i have formated my pc 2days ago
xD
Thankx for this pack nandlal_mk
It was good if it was more options to cook our proprly rom
Click to expand...
Click to collapse
Im still on improvement work, especially option to choose Language Packs via OEM packahe and more on registry changes, but the limitation is of time. I have free access to my PC only in night for 2Hrs
I answered my question by myself: it's explained in the PDF-File!
But I got another question:
Can I switch the Core-ROM? I'm customizing at the moment PDAViet 4.0.0.0.3 but I think it's not all to replace the OS.nb inside the Kitchen! Explain it please!
animelover said:
I answered my question by myself: it's explained in the PDF-File!
But I got another question:
Can I switch the Core-ROM? I'm customizing at the moment PDAViet 4.0.0.0.3 but I think it's not all to replace the OS.nb inside the Kitchen! Explain it please!
Click to expand...
Click to collapse
Hi animelover,
Nice to see u.
I have been out for some work and will complete remaining tutorial on first page.
Well, choice for Core rom just arises cuz i liked its speed and performence even when there is not much registry changes, i changed very little few reg to work with prophet, as it was consuming time of my work hour.
And its absolutely possible to port any custem rom to kitchen, that was my search which ends in a shape of this kitchen.
But as i stated in 1st post we should have a official WM6 for prophet then only the kitchen based on that will be perfect.
There is some inbuilt behaviour of BuildOS.exe, that it does not construct registry based on custom rom that has been ported to kitchen, rather it construct registry from deployed SYS/OEM structure.
Thats why when a custom rom ( say Smart1 v3 or any) ported in kitchen vanishes its customized registries on running BuildOS.exe, and newly created rom will have totally different registries than original one.
However original registries of custom rom r placed in SYS/Metadata but they r ignored during BuildOS.exe (Mods, please correct my findings if im wrong)
If there is a better chioce for a rom that should be ported, please mention, that will be ported in RK, but u know what i wrote above.
One has to make registry changes after BuildOS.exe to make rom more performative.
it looks promising,
when will tut on post#5 complete ?
Reduce imgfs size and put more OEM/Files
Extract Zip and replace TOOLS dir and CreateROM.bat with old one in RK.
Modified File/TOOLS are optional, one can continue to work with old ones.
Benefits & Facts of Enhancement #(1)
.....(1) Modified File/Tools repack imgfs block and hence OS.nb to reduced size!!
....(2) Standard size of Shiped OS/Old cutom cook OS is 58368 KB(59,768,832 Byte)
....(3)With modified File/Tools new OS.nb can be as less to 50 MB!!
....(4)Hence its possible to include more OEM Packs and files untill the limit of 58368 KB
....(5)Decrease in imgfs block does not grow Storage on flashed device.
....(6)If OEM Packs/Files r deleted, initflashfile.dat must be edited, if not then device could not be booted properly
....(7)Flashing reduced size OS.nb with FlashOS, may not prompt completion, so one has to wait as long as to approx 30 min or above to make it complete in hidden mode.
....(8)If too many OEM/Files included than these tools make OS.nb greater than standard size without any error, but avoid such OS and dont risk ur device by flashing over size OS.nb
....(9)My 2 days experience with reduce size OS.nb--- device switches off frequently after waking up, no other issue found yet.
Brakelseboer said:
This ROM is great. Beautifull bootscreen and finally sound for every tap, even the Start Menu.
One Problem:
When I change the backlight setting (everything off) and I switch off and on my device the backlight is gone. The only solution is to hard reset my device and set it up again. Is there a solution for?
Click to expand...
Click to collapse
there is no such problem on my device, but its possible different devices shows little variation in performence.
try using without backlight off setting or power offsetting for some time, i think it may help or remake-reflash in freash way.
im still on enhancement work, but with slow pace. However there is not much to change as base rom provided by anichillus is already superb.
But still i will post some more enhancement before reviving whole kitchen with any new good base rom.
Thread move to WM6 section, will update and clean later
Good work nandlal_mk
thanx for sticky
Jesterz said:
Thread move to WM6 section, will update and clean later
Good work nandlal_mk
Click to expand...
Click to collapse
Thanx Jesterz.
Its nice to see you again after a long time ( last activity 20-3-07 , i was eying/waiting to change it), really missing u all prophet forum user.
I need ur assistence, may i PM u later?
nandlal_mk said:
Thanx Jesterz.
Its nice to see you again after a long time ( last activity 20-3-07 , i was eying/waiting to change it), really missing u all prophet forum user.
I need ur assistence, may i PM u later?
Click to expand...
Click to collapse
Thanks ! and sure, give me a PM whenever
C ya
2 questions...
1. can i use this tool to cook ipaq rom?
2. if the pda has no phone function, how can i remove the phone module?
sorry i am newbie, pls bear with me if i asked silly questions
Anyone have the problem on the status battary?
nandlal_mk said:
Im still on improvement work, especially option to choose Language Packs via OEM packahe and more on registry changes, but the limitation is of time. I have free access to my PC only in night for 2Hrs
Click to expand...
Click to collapse
Please let me know if you need help for multiple lingual packs as I know japanese, korean and chinese. I still have the problem of doing a korean/japanese language rom. Tks!
Is there a way to convert OEM Packages into cabfiles that I can install like any other program?
OEM to cab
Infestor said:
Is there a way to convert OEM Packages into cabfiles that I can install like any other program?
Click to expand...
Click to collapse
I use this program for making cab files
Installation Creator
It's got everything you need
Just place the files in the right folder and edit the registry and go to build and your done
new core rom
I realy like to get a new core rom the one inside this kitchen is buging me.. as is restarts the prophet rapidly
Thanks gullum!
I only have some remaining questions:
First, is it correct, that the registry entries from the OEM-package are in the *strange-hex-code*.rgu? Do I need to enter this code anywhere? Is there a way to import this file directly into the Installation Creator or do I have to add the settings manually by editing the registry sections?
Second, how can I find out if there are any self registering or setup dll files that I have to specify during the setup process?
Sorry to bother you, if there is a thread or tutorial where this has been discussed before, just tell me which one it is.
I just downloaded the OEM.zip from the Wizard Forum and want to try some of the programs out.
Thanks again for your help!
PS: And yes, I have the same problems with the core here...my Prophet restarts every 10 inutes or so .
Help me
gullum; said:
I use this program for making cab files
Installation Creator
It's got everything you need
Just place the files in the right folder and edit the registry and go to build and your done[/QUOTE
Bro, thanks for the link but i dont really understand how to create cab file using this intallation creator tool but eager to try. I'm quite blur. Can you help me on this?
Click to expand...
Click to collapse
ATOM WM 6 AND WM 6.1 ROM COOKING TUTORIAL
nb: try it at your own risk,.
WHAT DO YOU NEED?
- Hypercore Kitchen
- Garmin XDA ATOM ROM Cooking Sets (UPDATED 14/03/08)
ADD-ON
- WM 6.1 SYS files
Usage Of Hypercore Kitchen
- Creates OEM and anything related to OEM
Usage of ATOM WM6 Kitchen
- Dump your diskimage_ver.nb0
- Build your new diskimage_ver.nb0
Already have it all?? Alright, now lets start working,.
1. Extract "Garmin XDA ATOM Cooking Sets" to somewhere you like, (There will be an original OEM and SYS folder, don't erase those, it required for dumping process,.)
2. Put your diskimage_ver.nb0 into ROM folder, (overwrite the original file there,.)
3. Run "DumpFiles.cmd" , (Then you'll see a working progress, until it ask you to press any key) ---- press any key then,.
4. There will be a new window come named "Package Tool", then Open where the "dump" folder is located, (The package tool help you build your OEM and DSM,.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Go to \Tools\Build Package, you will not see a working progress, when the content of the Package tool was changed, ITS DONE!!, and your diskimage_Ver.nb0 was dumped,.
(The original OEM and SYS folder will be gone,.)
--- Now go to "dump" folder and you'll see OEM and SYS folder ---
nb : If there are some files outside OEM / SYS folder, put it where it should by reading the last line of your package tool, after building a package,.
----------> means that these file should be in \SYS\NetCF folder,.
OKAY, take a rest first, have some experience with that OEM and SYS folder,.
You may change, add or remove some folder there, but BECAREFUL, some of them are SYSTEM file!!!
Satisfied experience with OEM and SYS folder?? Lets Continue,.
6. Now move your OEM and SYS folder (inside "dump" folder), to the first page (Where the original OEM and SYS is located)
7. Run "BuildOS.cmd" (You will see a new window "BulidOS",.) press the green button,.
8. When done, (you could see on the bottom left corner, written "Done"), close the BuildOS by pressing the [X] Button, (dont close the BuildOS.cmd)
9. You will see in the BuildOS.cmd, a progress, wait till it ask you to press any key,. ----- Press any key then,.
10. There you are, your new diskimage_Ver.nb0 is inside "FLASH" folder,.
Nb: For a tutorial about building an OEM, could be seen HERE, and How To Port XIP and SYS folder, could be seen HERE,.
nb: For WM 6.1 Cooking, you couldn't DUMP your ROM, because it removes all manifest to be one,.
GOOD LUCK,.
Happy ROM Cooking to all of you,.
- Kumara -
STICKY IT!!
udayrulz said:
STICKY IT!!
Click to expand...
Click to collapse
Thanks mate,.
the problem is where you get "your diskimage_ver.nb0" ?????? you will have to use an "already built" diskimage_ver.nb0 (like jiggs') and modify his rom, you can not create your own rom with another build like 5.2.1933 or else, I was trying to make a new rom from a new build but I wasn't successfull. Jiggs told me to read the wiki, but maybe I didn't do my homework so well.
medkid said:
the problem is where you get "your diskimage_ver.nb0" ?????? you will have to use an "already built" diskimage_ver.nb0 (like jiggs') and modify his rom, you can not create your own rom with another build like 5.2.1933 or else, I was trying to make a new rom from a new build but I wasn't successfull. Jiggs told me to read the wiki, but maybe I didn't do my homework so well.
Click to expand...
Click to collapse
It shouldn't be any problem mate,.
You could use any diskimage_ver.nb0 to dump,.
look at my new ROM (O2 Atom WM6 Premium), it was dumped from jiggs WM6 AKU 0.7a,.
Just use mine mate, (from O2 Atom WM6 Premium), its dumpable,.
@Ckaidi
Exactly , although i have no way near the knowledge required to make 1 but ...i just did a quick background check on you and figured out that you hv been cooking for a while now....so yea i understand wat you lookin at..
This is really different from what we used to cook for xda 2. How I wish cooking for an atom is as easy as cooking for an xda 2.
Anyway, good luck to all who would like to attempt cooking their own ROM. I'll just look at those available in here and copy those that I think will fit me best.
BTW, I hope somebody can teach me how to change the splash images. I would like to replace them with pictures of my family.
^welcomehead.96.png = splash image..
found in SYS folder..
Garmin said:
It shouldn't be any problem mate,.
You could use any diskimage_ver.nb0 to dump,.
look at my new ROM (O2 Atom WM6 Premium), it was dumped from jiggs WM6 AKU 0.7a,.
Just use mine mate, (from O2 Atom WM6 Premium), its dumpable,.
Click to expand...
Click to collapse
I know it,I know that your diskimage_ver.nb0 is dumpable (don't you see the rom I built pReDrT ?)
what I want to say is , you can not build your own diskimage_ver.nb0 based on a new build (for example 5.2.1933, the newest build), what you do is dumping a built diskimage_ver.nb0 from jiggs (the original one) which's build is 5.2.1908, don't you see that ???????
To build a new rom with a new build, it costs an arm and a leg, so much time spends on it. It's not easy as you said,but I really appreciate what you share here.
bro,
where's the part of the dump do i go to add new appz or new files?
the guide is just like extracting and compressing thing but how we add something?
where's the folder structure of \windows , \program files , etc..?
please update the pics too..it's much easy to do it with visual guide..
guide us please..
thanks a lot..
-=[serialzs]=-
You have to add them in OEM folder mate...
udayrulz said:
You have to add them in OEM folder mate...
Click to expand...
Click to collapse
and where do it go in our unit if we update???
can you be more detailed? is there a \windows and \programfiles folder in OEM folder?
thanks..
-=[serialzs]=-
serialzs said:
and where do it go in our unit if we update???
can you be more detailed? is there a \windows and \programfiles folder in OEM folder?
thanks..
-=[serialzs]=-
Click to expand...
Click to collapse
Yes , the files go to windows directory automatically
First download Ervius Packages Creator..
..say you want to include TCPMP in your ROM , You first need to Unzip all the files that TCPMP installs to a folder ..now open Ervius Packages Creator..navigate to folder .add a shortcut (option in the packages software..)
and click create package..now copy the folder to the OEM folder and build ROM..
Hope you get the idea..
yes i get the idea..what if i want to install it in program files folder? what should i do?
sorry for making ask again..i want to know it so that i can help you guys too..
thanks a lot..
-=[serialzs]=-
I dont know that ....sorry...
You can obviously create Custom Cabs and run put em in extended ROM for installing in program files..
You can search for OEM packages on the site.. u ll find plenty...
I am still learning so do pass on the knowledge..
Going a bit OT - Are you the one who made the DSU installed for ROM installation??
serialzs said:
yes i get the idea..what if i want to install it in program files folder? what should i do?
sorry for making ask again..i want to know it so that i can help you guys too..
thanks a lot..
-=[serialzs]=-
Click to expand...
Click to collapse
you will specify it in initflashfiles.dat, but you will have a double copy. The purpose of putting it to ROM is to have all the applications you need and consume less persistent storage vis-a-vis installing the cabs after a hardreset. However, having too many files in \windows will cause your system to lag; so, this is the purpose of utilizing the extended ROM wherein the skin files (like wireless manager / htc home / mediaplus) can be placed in the extended ROM and the program files in \windows.
serialzs said:
bro,
where's the part of the dump do i go to add new appz or new files?
the guide is just like extracting and compressing thing but how we add something?
where's the folder structure of \windows , \program files , etc..?
please update the pics too..it's much easy to do it with visual guide..
guide us please..
thanks a lot..
-=[serialzs]=-
Click to expand...
Click to collapse
To add a new appz, you have to make your appz (appz that you would like to have as a default appz) as an OEM,.
How do we make an OEM? i am working on it, i'll post it here soon,.
all the files there (inside SYS and OEM folder) will go to windows directory, then if you would like to move something to program files directory, you have to make an "initflashfiles.txt",. (usually for your OEM)
for example,
Directory("\Windows\StartUp"):-File("coldinit.lnk","\Windows\coldinit.lnk")
----- > it means that you copy file "coldinit.lnk" to \windows\startup folder,.
hope that help you,.
serialzs said:
and where do it go in our unit if we update???
can you be more detailed? is there a \windows and \programfiles folder in OEM folder?
thanks..
-=[serialzs]=-
Click to expand...
Click to collapse
It wont go anywhere, as long as we dont make a "initflashfiles.txt" for our apps (that have been changed to OEM), the shorcut of the apps wont go anywhere, it still in windows folder, (so, it wont be displayed in the main menu)
medkid said:
I know it,I know that your diskimage_ver.nb0 is dumpable (don't you see the rom I built pReDrT ?)
what I want to say is , you can not build your own diskimage_ver.nb0 based on a new build (for example 5.2.1933, the newest build), what you do is dumping a built diskimage_ver.nb0 from jiggs (the original one) which's build is 5.2.1908, don't you see that ???????
To build a new rom with a new build, it costs an arm and a leg, so much time spends on it. It's not easy as you said,but I really appreciate what you share here.
Click to expand...
Click to collapse
Ow i see,. sorry missunderstanding,.
Yep, absolutely you could, i am working a new ROM with upgrade of XIP to 5.2.1933 at the moment, if it success, i'll update the thread,.
but it havent finished, so the thread just till extracting and repacking,.
Gud luck,.
Download View attachment package-creator-v27.zip
After downloading the package creator Extract to any folder and run package-creator-v2.7.exe. Select language and select group to insert package. Here The group reffers to Programs. You can add or edit lang.xml to add or delete groups.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then click on Open Cab File and navigate to your cab file and Click Open.
Wait until it shows you done Confirmation window. Then navigate to the cab folder and you will see new folder with OEm package. This tool will generate initflashfiles.txt, option.xml, .dsm and .rgu for the kitchen ROM.
Copy the OEM package to your kitchen and have fun with customizing your Rom
(found this somewhere on internet, correct me if i m wrong)
Great work! Nicely done tut. Here is another method to do so. This one is a bit faster but it doesn't always works.
Cab2OEM is also a free software that can be used to convert cabs to packages. This software is a command-line utility with no GUI but it does its job pretty well.
Cabs are of two types, the older ones with an inf file with extension .000 inside that describes the installation process and the newer ones with a _setup.xml files. Cab2OEM works on XML ones only.
Usage:
Its simple, just fire up a command prompt and run this command:
Code:
Cab2OEM -f <path to cab>
Here, replace path to cab with a real path. In a few seconds, it will convert the cab into a folder in the current directory.
NOTE: Cab2OEM creates an option.xml file inside the package which provides a description to the package that can be seen while running build os. but by default, it doesn't adds the package to the buildos list. I recommend you to delete this file.
This method is not as advance as Package Creator but its a quick and dirty one Package Creator can work with all cab files.
The file is attached with this post.
Great Work
Good going man....
Can you suggest some good and easy Kitchen for old gene..
Can i also include cracked applications...in custom ROM
Ramerson's kitchen is the easiest one i have ever seen. But the whole process of cooking ROM can never be easy, no matter which kitchen you use.
We strictly dont support cracking etc here so no answer for that.
Many thanks Krazy.......
Can ur ROMs be used to delete some packages and include some freewares...
please guide me about the pagepool.....what are disadvantages of increasing or decreasing it...does it help in increasing RAM....
I read about a thread which says RAM can be increased by deleting ExtROM...
Your expert comments please....
Also the Ramerson's kitchen link and "How to gude" if possible........
That would be nice of you....
Heres a quick response:
1. Yes my roms can be dumped and modified as per your needs. The only thing you need is the knowledge of how to dump them properly for recooking. For that refer to ramerson's tut.
2. Pagepool is that reserved part of memory that is never available for the programs to use and iit is used by the OS to maintain its internal state, data structures and so on. More the pagepool memory, more resources the OS will have and more simualtaneous running programs you can have. But this clashes with the fact that programs also need RAM for other purposes other than the OS provided resources. So the contradiction is that you cant run more programs simualtaeously id you have less RAM. So increasing Pagepool decreases RAM but increases OS resources, Decreasing page pool increases free ram and decreases OS resources. Chefs have to keep a balance between that. For gene, 6 MB of Page Pool is recommended, keeping in mind all the specs of the devices. Pagepool has to be changed everytime you recook the ROM as of now.
3. My ROMS use 4 MB of ExtROM and that is optimal, by default you have 10 MB of ExtROM. SO no need to messup with that, device doesnt boots with extroms smaller than that. Ramerson has also confirmed this.
4. Ramerson Kitchen is a seprate thread in this same forum, use your eyes and mind for that. How to Guide is currently not available as step by step, but Ramerson's tut which is a sticky post, will help you greatly.
I hope my answers helped.
o my god my head is spinning
hi guys
i tried reading all this and my god o god my head went for a spin i think for me to do any thing cook rom and all this in this chapter will take me a long long time of reading which im realy not great at
but reading all this give me more repect for Krazy,ankit,ramersnow and all u great techi guys
u guys are great man hats off to all off u and thanks a million
^Thanks Hari. Actually the gene you are having in your hand is not very less complex than any other computer. So apart from some basic differences, most of the elements of computer engineering can be applied to this small buddy as they are applied to computers. Thats why it seems so darned techie, coz it is techie
i meant every word
hi
to all u great contributors to this great forum i thing all these tuts available are a great eye opener to a totally non techi guys like me who uses ur great services which you actually do for free i having read many many tuts have clearly understood the time u are spending for us to enjoy and i really really say from my heart hats off to u guys and thanks for ur great contribution
and in the future when things get better for me i will start donating
and the funny thing is i sell computers for around 10+yrs
but this info in the tuts is a total head spinner for me
getting to next level
Great Krazy....
U r true krazy about technology......
To run emulators like SPB Mobile shell in best performance what should be optimum pagepool....
New version of Package Creator
Please find newer version of package creator, Version 5.4 to be exact
http://wiki.xda-developers.com/index.php?pagename=OEM Package Tutorial
Thanks man! this will really help
imblfmstr said:
Great Krazy....
U r true krazy about technology......
To run emulators like SPB Mobile shell in best performance what should be optimum pagepool....
Click to expand...
Click to collapse
SPB Mobile shell is not an emulator, its a shell replacement which actually runs on the top of the existing shell32.exe shell. There is no extra page pool requirement for it to run. 6 MB would be fine.
Cab Maker
Useful application for Making Windows CE compatible cab can be found here: http://forum.xda-developers.com/showthread.php?t=400221. It can be used by developers as well as cook.... OOPS Chefs
Another alternate is http://www.ocpsoftware.com/downloads/cecabmgr/CeCabMgr_Setup.exe
Could any One tell me how to make my own package and add it to ROM while cooking , or the link that i can found this
I already use the tools that mentioned here but while cooking process going on it give me an ERROR ( I use the cooking way in -[TUTORIAL]How to cook for GENE-)
Thanks in advance
facing one problem in cooking a ROM...
every time i add a custom package ...and then i run "build OS" i get an error
"Error in building in default.hv and user.hv"
and i if remove the content of .rgu files from the custom packages it run fine..no issue...
i am using the "package-creator-v2.7" to create packages..i want to have some registry settings in ROM...
Please advice how to overcome this issue....
orange2784 said:
facing one problem in cooking a ROM...
every time i add a custom package ...and then i run "build OS" i get an error
"Error in building in default.hv and user.hv"
and i if remove the content of .rgu files from the custom packages it run fine..no issue...
i am using the "package-creator-v2.7" to create packages..i want to have some registry settings in ROM...
Please advice how to overcome this issue....
Click to expand...
Click to collapse
I do not have a straight solution for this, But here is what I did, I exported the registry key, saved it as rgu and then used package manager 5.4 to make it into a package.
Registry file is not properly formatted. Keep following points in mind :
1. Registry file (.rgu) must be in unicode format, not ANSI, which is the default saving format of Windows Notepad. You can change it in the save file dialog of notepad.
2. The file must begin with the word REGEDIT4 in the first line saperately.
3. There should be atleast one or two blank lines at the end of the file.
4. Entries in the files should be properly formatted. Following are the general values and their formattings that you will find in rgu files :
a. Path to hives must be covered in square brackets, ex : [HKEY_LOCAL_MACHINE\Software\Microsoft]
b. All string values must be formatted like this : "Name"="Value". If there is a file path inside the string, it should be having \\ instead of \ as separator. Ex: "FilePath"="\\Windows\\AudioManager.exe"
c. All DWORD values should be in this format : "Name"=dword:8 digit number. Ex : "BacklightOff"=dword:00000001
d. All binary values should be formatted as : "Name"=hex:v1,v2,v3,v4...... Ex: "AValue"=hex:00,00,11,01,10
Follow these guidelines and your registry file will compile fine.
Thanks a lot Krazy...thats a valuable information .... i ll check the rgu files ... correct them and give a shot.....
and thank you Addicted2xda for your inputs... i ll try this one also ..
Also please note, inside the dump folder, there is a text file that contains the error log. The last 2-3 lines of this file actually describes in which file the error occured. Actually the Windows Mobile Registry is compiled from rgu files using a program called rgucomp.exe and is stored in files ending with extention .hv. Just for your information
Good luck!
Hi,
sorry but my English is not very good.
I configured the kitchen for our phone.
The kitchen is ready to create a Rom and it include:
SYS 23569 En/It
XIP 23568
OEM 3.003c En/It
some EXT package for example
ACER_EUU (includes the latest patch for GPS)
I added these tools:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Build extrom.bin:
insert your cab files in the EXTROM folder;
click on Build extrom.bin;
look inside the RELEASE folder.
Note: I wrote a small program that automatically creates the file CABPIACB.pil according to these rules:
the file extension is not displayed during the installation process;
the character underscore is replaced by space (the space character in the file name is not allowed by the acer's installation program);
you can sort the files by entering the prefix 0_, 1_, 2_ .... 9_, a_, b_ ... z_. For example:
Dump Acer_S200.amf:
insert your Acer_S200.amf (with this exact name) in ROM folder;
click on Dump Acer_S200.amf;
look inside the DUMP\AMF folder.
Dump extrom.bin:
put your extrom.bin (with this exact name) in ROM folder;
click on Dump extrom.bin;
look inside the DUMP\EXTROM folder.
Dump flash.bin:
insert your flash.bin (with this exact name) in ROM folder;
click on Dump flash.bin;
look inside the DUMP\FLASH folder.
Instructions for cooking:
install OSBuilderSetup.msi
to start the kitchen open the file OSBuilder.osb
select your language (0409 = en, 0410 = it)
mark / unmark ext package
click on start button (play)
wait...
look inside the RELEASE folder
XIP porting:
very simple, change only these folders:
- ROM\XIP\MSXIPKernel;
- ROM\XIP\MSXIPKernelLTK.
Download:
- OSBuilder Setup v1.0.94
- Kitchen
Much more information can be found in the original thread.
Note:
- I'm not sure if my configuration is the best but for me it works very well.
- For this kitchen files with .dsm extension (not used in Rafyvitto's kitchen) are very important. Very useful is the command DSM autocorrection.
Thanks to:
- Barin for this kitchen and for helping me to configure it;
- Rafyvitto for the first kitchen;
- Alexx~ for helping me to configure this kitchen;
- bepe, Weisun, Anper, Stark Wong, DimICE for their tools.
Good cooking
emm...
But the download link just shows 404 for me...
But, seems that just a few tools could be enough to cook a good rom for a good cook
Understanding the process could be more easier to handle for advance levels lol
for me too, what kind of improvment can we get compared to the rafy kitchen? a faster cooking?
Arto said:
for me too, what kind of improvment can we get compared to the rafy kitchen? a faster cooking?
Click to expand...
Click to collapse
I think GUI kitchen could well organize the packages for multi ROM...
It seems that the advance controls could be more easier to handle than form CLi
Nagato Yuki said:
emm...
But the download link just shows 404 for me...
Click to expand...
Click to collapse
Yes,
but I downloaded this:
Link to my CDMA TP2 kitchen
Click to expand...
Click to collapse
I gave a link brainmaster to your own kitchen S200 on Osbuilder with Russian localization package 0419
feropont said:
I gave a link brainmaster to your own kitchen S200 on Osbuilder with Russian localization package 0419
Click to expand...
Click to collapse
Can you give us the kitchen you mentioned? I'd like to try it.
Thank you.
It is a very good tool, and handles module reallocation better than any other kitchen that I've seen to date. Also has many features not found in any other kitchen. It is a superior tool, and in my opinion builds superior roms. Barin is supporting the tools well, and has great updates with additional features on the horizon, including the multi-build feature. You can download the tools, including the installer from my kitchen here, which includes everything except sys and oem, but keep in mind that I build for a HTC device, and so have it set to build to .nbh -- you may need to change settings for your device:
http://www.mobileunderground.info/indagroove/OSBuilder/OSBuilder Kitchen Tools.7z
I added my kitchen on the first post
Stefano_1986_ said:
I added my kitchen on the first post
Click to expand...
Click to collapse
Amazing work !!!! I will give it a try !!Thx for this contribution
hm I'm near from start cooking but I don't know what to do with the .rom and .vm folder that I have to add in SYS folder in the rafy kitchen, Idea?
Arto said:
Amazing work !!!! I will give it a try !!Thx for this contribution
Click to expand...
Click to collapse
You are welcome
Arto said:
hm I'm near from start cooking but I don't know what to do with the .rom and .vm folder that I have to add in SYS folder in the rafy kitchen, Idea?
Click to expand...
Click to collapse
You can delete these folders
Stefano_1986_ said:
You are welcome
You can delete these folders
Click to expand...
Click to collapse
Ok ! I get an error with module winsock.dll "this module can be corrupted"
Have I to recmod it?
edit : ok recmoded and it works
Arto said:
Ok ! I get an error with module winsock.dll "this module can be corrupted"
Have I to recmod it?
edit : ok recmoded and it works
Click to expand...
Click to collapse
I haven't recmoded any files and I haven't received any errors.
Stefano_1986_ said:
I haven't recmoded any files and I haven't received any errors.
Click to expand...
Click to collapse
its the only file with this error, I use the 21907, maybe the archive, I'm flashing right now
Arto said:
its the only file with this error, I use the 21907, maybe the archive
Click to expand...
Click to collapse
maybe... I haven't tried that build.
Arto said:
I'm flashing right now
Click to expand...
Click to collapse
But, I don't like having to install it before use, is there any portable version?
Nagato Yuki said:
But, I don't like having to install it before use, is there any portable version?
Click to expand...
Click to collapse
I don't know.
You can ask at the developer.
Flashed but like all the first times, I get some issues, windows boot no problem, today screen, no problem, but the settings menu is half missing and sense does'nt launch, I think there is a problem with my sys but don't know why
edit: I copy/paste my SYs a second time and now, there isn't corrupt modules, the modules appears to be very sensitives when I move them
Sorry, my English is not good! I want to say is that great kitchen, it also gives me great inspiration, if you interested, we will bring you from China Kitchen