aChef ROM Utils ver 0.2.1 (beta) - 8525, TyTN, MDA Vario II, JasJam Software Upgradin

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!

Related

Finally: New Tool - Cook your own (ext.) ROM for XDA2

Hi,
since my extended ROM is locked and I really wanted to customize my extended ROM (=collect the best from all available versions without the crap), I created a tool which is called ER2003Edit.
You can use this tool to:
- Display the header information
- Extract and modify the splash bitmaps
- Completely modify the contents (=extract, delete, import, rename) via
Drag'n'Drop
- Automatically calculate the checksum during save (thanks to Itsme for
finding out the details!!!)
What this tool can't do:
- Edit other ROM images than the extended ROM for the xda2
(support for editing the OS image may be added later)
- Modify the header information
(may be added later)
Just install and try....
Please not that this software hasn't undergone thorough testing, so
please be careful, use at your own risk! Only thing I can say for now
is that it worked for me!
Have fun!
Update: A new version has been released! Please have a look at the ER2003 wiki page for more information:
http://wiki.xda-developers.com/wiki/ER2003Edit
Thank you so much.
It's easier than do with linux.
{
"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"
}
softworkz said:
Hmm, uploading does not work, until this is fixed you can try to download
from ftp://xda:[email protected]/ER2003Edit.zip
I will update this post when there will be a better way for downloading,
maybe the guys from the forum here can install a fixed download page,
when searching in the forums you never know if you got the latest version...
Click to expand...
Click to collapse
Whoops, we had a permissions problem. Fixed now...
Program looks positively excellent.
Hi,
softworkz said:
since my extended ROM is locked ...., I created a tool which is called ER2003Edit.
You can use this tool to:
- Display the header information
...
What this tool can't do:
- Edit other ROM images than the extended ROM for the xda2
(support for editing the OS image may be added later)
...
Click to expand...
Click to collapse
softwarkz: do you think that you program might work with the MDA II as well?
Is there someone who tried ER2003Edit with a MDA II ?
Thanks
bauruine
MDA II is the same as XDA II.
Tested it, works.
Nice piece of software!
As already mentioned, you still need to change the header with xda2nbftool to use an O2 rom on a T-Mobile device and vice-versa.
I you mod the rom contents, I suppose it is best to also mod Config.txt?
don't know if I posted this before, but inspecting the fat filesystem at low level reveals that there are many other 'hidden' / deleted files stored in the extended rom, a wrote this perlscript : fatinfo.pl
to examine the contents of fatfilesystem image files. and optionally extrect the deleted files from it.
Itsme said:
don't know if I posted this before, but inspecting the fat filesystem at low level reveals that there are many other 'hidden' / deleted files stored in the extended rom, a wrote this perlscript : fatinfo.pl
to examine the contents of fatfilesystem image files. and optionally extrect the deleted files from it.
Click to expand...
Click to collapse
I found one bug while saving
Error occured at: 2004-01-28 15:52:50
Component: ER2003Edit (ER2003Edit)
Version: 1.0.12
Modul: frmER2003Edit - mnuSave_Click
OS-VErsion: Build:3790
Error: Automation error
The specified module could not be found.
but the files has been save and i try to upload it to my XDAII and it works fine. I am using "Windows 2003 Enterprise edition" is this because of my OS?
Ronnie
Looks great - plan on giving it a try ASAP!
Thanks!
how abt the xda I....
dont forget us out there... how can i make this work for the xdaI where most of the files i have are nb1 extension... any clues would love to be able to use this...
rpc said:
I found one bug while saving
Error occured at: 2004-01-28 15:52:50
Component: ER2003Edit (ER2003Edit)
Version: 1.0.12
Modul: frmER2003Edit - mnuSave_Click
OS-VErsion: Build:3790
Error: Automation error
The specified module could not be found.
but the files has been save and i try to upload it to my XDAII and it works fine. I am using "Windows 2003 Enterprise edition" is this because of my OS?
Click to expand...
Click to collapse
After a file is saved the program calls the xda2tools.dll to update the checksum. There are 2 reasons why this may fail:
1. xda2tools.dll was not registered by the setup.
Try: regsvr32 xda2tools.dll
2. One of the dependencies weren't installed correctly.
Please verify that both "msvcr70.dll" and "msvcp70.dll" were installed
to your Windows\System32 folder. During tests I noticed a problem
where the latter file was installed to C:\ instead of the system32
folder but I thought that was fixed...
PS: I really wonder that flashing worked without updating the checksum...
Please tell me if it works now. Did others have the same problem?
softworkz
Jos said:
MDA II is the same as XDA II.
As already mentioned, you still need to change the header with xda2nbftool to use an O2 rom on a T-Mobile device and vice-versa.
Click to expand...
Click to collapse
A feature for editing the header information will be added!
Jos said:
I you mod the rom contents, I suppose it is best to also mod Config.txt?
Click to expand...
Click to collapse
Yes you absolutely need to do this. Auto-generation of the config.txt would be nice, too. I currently just haven't got enough information if there is a certain order in which some of theses components need to be installed.
Re: how abt the xda I....
rc said:
dont forget us out there... how can i make this work for the xdaI where most of the files i have are nb1 extension... any clues would love to be able to use this...
Click to expand...
Click to collapse
Unfortunately xda1 is currently not among my top priorities, so it may take a while until you could expect support for this.
Re: how abt the xda I....
softworkz said:
rc said:
dont forget us out there... how can i make this work for the xdaI where most of the files i have are nb1 extension... any clues would love to be able to use this...
Click to expand...
Click to collapse
Unfortunately xda1 is currently not among my top priorities, so it may take a while until you could expect support for this.
Click to expand...
Click to collapse
i can help if u want... i can code some too,pm me if u would like me to try
Some questions
Hi there,
I'm currently thinking about adding support for editing the NK.nbf as well. What do you think, would this be required?
What I personally would like to do is
to be able to change the keyboard layout - my current guess is that this depends on the file compime.dll
to be able to change the dictionaries for word completion to another language - haven't figured out yet where this is stored
What do you think?
I am running xp pro, downloaded and installed the program, when I run it the main screen for rom edit appears but nothing responds to clicks. Am I missing something? XDA2 is connected and activesync is running.
cruisin-thru said:
I am running xp pro, downloaded and installed the program, when I run it the main screen for rom edit appears but nothing responds to clicks. Am I missing something? XDA2 is connected and activesync is running.
Click to expand...
Click to collapse
This software does not edit the "live" extended ROM on your device. It allows you to edit the ms_.nbf ROM image file that is included with the software upgrade tools.
To edit this file, start the upgrade program and wait until the files are extracted to the temp folder (like C:\Documents and Settings\username.DOMAIN\Local Settings\Temp\pftwxxxxx).
You use "File=>Open" to open the ms_.nbf found in this folder.
softworkz
Sorry, you have lost me completely, I downloaded the program, it installed itself, I cannot find any files that you mention, do I need to download something else. As I said before none of the buttons work in the program, "file" "tools" "help" are also greyed out. The only way I can close the program is ctrl alt delete, process manager says program is running then program is not responding when I tell it to close.
cruisin-thru said:
Sorry, you have lost me completely, I downloaded the program, it installed itself, I cannot find any files that you mention, do I need to download something else. As I said before none of the buttons work in the program, "file" "tools" "help" are also greyed out. The only way I can close the program is ctrl alt delete, process manager says program is running then program is not responding when I tell it to close.
Click to expand...
Click to collapse
Hehe, you just need to click on the splash screen or simply press any key to have it disappear and start working
btw: - any1 do have a backup of ext rom contents from T-Mobile Austria MDAII ? - hardly searching for it!
Asterix said:
btw: - any1 do have a backup of ext rom contents from T-Mobile Austria MDAII ? - hardly searching for it!
Click to expand...
Click to collapse
Here it is! And also the ExtendedRom XDA2 ONE Austria 1.60.19!
Have fun!

WM6 Rom Kitchen

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

[TUT] XDA Atom WM 6 and WM 6.1 ROM Cooking

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,.

[Tutorial + Links] The new s600 touch.dll cooked into roms

I got my Touch Dual last Thursday and knew nothing about it and here I am, still know nothing But I do know you need to have your device CID unlocked or whatever. You know the drill, and if you don't. Search.
Right, a kind fellow from this thread here provided us with a touch.dll (some sort of display driver) from a Dopod s600, or commonly known as touch dual. What's so good about it? It's the best driver we've got as far as I know.
I've put it into these 3 roms:
Niki Project Rom v1.0 WM6.1 CE OS 5.2.19716 ( Build 19716.1.1.0 ) WITH NEW DRIVER
Mirror 1
http://asapload.com/112873
WM6.1 Mary v0.2 OS 5.2.19716 (Build 19213.1.0.4) WITH NEW DRIVER
http://asapload.com/112868
WWE Asia
http://www.ziddu.com/download.php?uid=Z7OglZysaq2bnOKnYaqhkZSqXqydmZyu1
German Shipping ROM (thanks to mactron )
http://rapidshare.com/files/117870556/RUU_Nike_HTC_DE_1.31.407.09_Ship_s600_touc.dll.rar.html
US Niki 6.1 v1.0 w/ S600 Touch.dll implemented by mactron
I have not tested this rom personally. please see mactron for issues within this ROM.
rapidshare: http://rapidshare.com/files/12032683...h.dll.rar.html
megaupload: http://www.megaupload.com/de/?d=8X38BXT7
Nike_Original_NLD_ROM_v1.31.404.09_Patched_Touch_DLL.exe - Neliz
http://rapidshare.com/files/120248548/Nike_Original_NLD_ROM_v1.31.404.09_Patched_Touch_DLL.exe.html
Don't ask me why the size varies so much when the difference in the dll files is like 2kb. It works (I say that meaning, for me) so just go with it.
Pretty much, I was trying to use "kaiserkitchen_01-20-08" to do it but had problems rebuilding with BuildOS etc. I just didn't get it. I found this guide here and followed it. It's not hard. but I will copy and paste it and edit it to my own liking cause I changed it a bit and my bits are in blue. All of these tools come with kaiser kitchen. Think of your Niki as a Kaiser for now.
Andrew Green said:
Here comes Part 1 of the real nuts and bolts - the tools. It's all very well me spouting off about how much I've accumulated on the subject of .rgu files and all that....without the tools I'd know nothing.
The IMGFS Tools are without doubt at the centre of the toolset you'll use for cooking because they do all the real hard work associated with taking an .nbh file and splitting it open then taking a whole bunch of files and turning it into a single .nb file.
These tools are the product of two evolutions of the same idea, and certainly I'm indebted to the authors (Mamaich and Tadzio of XDA-Devs fame) for the creation and subsequent development of the toolset.
The Tools are (in order):
- NBInfo: which provides information about an .nbh file.
- NBHExtract: which extracts the various .nb files from within a .nbh file.
- NBSplit: Splits the OS.nb into its "payload" and "extra" portions.
- IMGFSFromNb: takes the IMGFS portion from an OS.nb.payload
- IMGFSToDump: extracts ("Dumps") all files from an IMGFS file.
- IMGFSFromDump: Reconstitutes the contents of a "Dump" into an IMGFS file.
- IMGFSToNb: Uses an OS.nb.payload as a road-map, in conjunction with a new IMGFS file, to create a new OS.nb.payload
- NBMerge: Creates a New OS.nb from the original Os.nb.extra and the new OS.nb.payload.
....and you're done!
....well not quite, you'll need the command lines. I've separated each part of the process into manageable chunks, ordered the folders etc. so (hopefully) it's easy to follow.
NBInfo <nbh-filename> - this is only really useful if you get what the outputs are, and I don't universally. If you scroll up you can see some interesting stats, like where the IMGFS partition begins and where the XIP is located.
Didn't use
NBHExtract <nbh-filename> (or drag-and-drop) - this splits your .nbh file into its .nb components, and you can even take a look-see at the splash screen! Rename your OS.nb and copy it to the next folder. You'll also get a whole mess of other .nb files. Keep them or ditch them, it's your choice, if they're not there when you re-flash, these parts are not over-written, with the exception of ExtROM, which is left empty if you do an OS-only.
Grab your RUU_Signed, grab your tools and put them in a folder. Run cmd. Navigate to folder. Type "nbhextract ruu_signed.nbh" to get your "02_OS.nb" file and rename it to "OS.nb".
NBSplit -hermes|-kaiser|-titan|-wizard|-athena|-sp <nbh-filename> - look, no mention of Artemis (Orbit), so Orbit users can skip this step.
I typed "nbsplit -kaiser os.nb". I now have 2 extra files, os.nb.extra and os.nb.payload. Leave the extra for now, deal only with payload.
IMGFSfromNb <OS.nb-filename> imgfs.bin - this creates an IMGFS file from your OS.nb (now the fun part), called "imgfs.bin"
Type "imgfsfromnb os.nb.payload imgfs.bin"
IMGFSToDump imgfs.bin - this creates a folder called "Dump", and extracts all the files from your imgfs.bin into it.
(The eagle-eyed among you will note there's another app in there, RecMod.exe, this is used by IMGFSToDump to construct certain of the exe and dll files in the dump, don't worry)
Type "IMGFSToDump imgfs.bin". If you do not have "cecompr_nt.dll" in your folder with your tools it will not work.
Now you have a dump folder. This can be used to cook from. Put files in, take files out, edit files, it's your choice from here. However, as you might expect, if you were to play around too much with certain files, things may stop working later....
Now, this is the tricky bit. I replaced the whole touch.dll folder in "dump" with the new one. If you do not "g'reloc" the folder. Your Niki will freeze at the second splashscreen. I don't get g'reloc. I Never will. This is how I made it work for me.
In windows, have g'reloc in your folder with the rest of your tools. Rename your "dump" folder to "SYS". Open g'reloc. It should say "Total 411" or some silly number. If it says "Total 1", you've done it wrong and good luck cause I know nothing about it. Anyway, run it with default settings. Done. Rename your "SYS" folder back to "dump". Continue.
Now, to reverse the process, copy your entire "Dump" folder, OS.nb AND the 'imgfs.bin' you created in the last step to the next folder down, to begin reconstruction.
IMGFSFromDump imgfs.bin imgfs-new.bin - this uses the original imgfs.bin as a road-map to create a new one (creatively titles imgfs-new.bin) based upon the contents of your dump folder, and compresses the result.
Type "IMGFSFromDump imgfs.bin imgfs-new.bin" in cmd.
IMGFSToNb imgfs-new.bin OS.nb OS-new.nb - as you've probably worked out by now, this is the last-but-one step. This takes your imgfs-new.bin (itself constructed from your revised dump) and uses the original OS.nb as a road-map to create a new one.
Here is where it's different, if you just type imgfstonb it tells you the usage ... so ... we need to rename some files. Rename your original "imgfs.bin" to "imgfs-old.bin" and then rename your "imgfs-new.bin" to "imgfs.bin".
Now, rename your "os.nb.payload" to "os-in.nb.payload". Now type "imgfstonb imgfs.bin os-in.nb.payload os-out-nb.payload". Nearly done.
NBMerge -hermes|-kaiser|-titan|-wizard|-athena|-sp OS-new.nb - is used in conjunction with the "Extra" file created by NBSplit (remember this isn't necessary for Artemis/Orbit) to make a complete OS.nb.
Now, the usage of this tells us something completely different. Rename "os-out.nb.payload" to just "os.nb.payload". Oh and before I forget. DELETE OS.NB NOW. Now type "nbmerge -kaiser os.nb -conservative". This creates your new one.
Here's something to try. Get an nbh file and go through the process described above, without making any changes. Logically at least, you should get an identical OS.nb at the end - though don't be surprised if it's smaller because Tadzio has mastered the art of efficiently re-packaging stuff into an IMGFS file.
Click to expand...
Click to collapse
Now you have a new OS.nb file. Open up "htc rom tool". Select it and NO RADIO, it's already there! Type "NIKI***" in the model id box or it wont flash. Make sure there's not another "RUU_Signed.nbh" in your folder and save the new one as "RUU_Signed" ... or "RUU_Signed2" just to be safe. Then shove it in a flashing folder or use the kaiserkitchen tool to flash it. Done.
EDIT: There will be loads of edits but Mods, if you want me to take the file down as it's not really mine. Just say.
EDIT2: Oh yeah! Not responsible! For anything! Ever!
EDIT3: If the version of Toms ROM doesn't work. Try this one.
Wow! Nice work! But I think you forgot the link for this one:
WM6.1 Mary v0.2 OS 5.2.19716 (Build 19213.1.0.4) WITH NEW DRIVER
DaVince said:
Wow! Nice work! But I think you forgot the link for this one:
WM6.1 Mary v0.2 OS 5.2.19716 (Build 19213.1.0.4) WITH NEW DRIVER
Click to expand...
Click to collapse
Just testing it now. Give me a couple of mins =)
have some one make benchmarks??
NetrunnerAT said:
have some one make benchmarks??
Click to expand...
Click to collapse
I didn't. So I don't know if the driver is better for the Mary ROM yet. Valvarin established that it's better than the one in the Niki Project ROM though. Someone more experienced will be able to tell me i'm sure.
well done...!
So who can help me extract and upload oemdriver from s600 rom and put link here for me ?
I will add in my V2.0
Best Regards..!
Thanks
tom_codon said:
well done...!
So who can help me extract and upload oemdriver from s600 rom and put link here for me ?
I will add in my V2.0
Best Regards..!
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=392465
It's in there =) Sorry for taking your ROM. Hope you're ok with it. Wouldn't mind you checking it over to see if it's ok really. I've flashed it, dumped it and checked the filesize of the touch.dll to see if it matches the s600 one and it does. I'm just doing it for the Mary v0.2 ROM now (which works too by the way, had a bit of a hiccup creating the final NBH file cause the NIKI*** has to be capitals.) Will upload it all soon =)
xangma said:
http://forum.xda-developers.com/showthread.php?t=392465
It's in there =) Sorry for taking your ROM. Hope you're ok with it. Wouldn't mind you checking it over to see if it's ok really. I've flashed it, dumped it and checked the filesize of the touch.dll to see if it matches the s600 one and it does. I'm just doing it for the Mary v0.2 ROM now (which works too by the way, had a bit of a hiccup creating the final NBH file cause the NIKI*** has to be capitals.) Will upload it all soon =)
Click to expand...
Click to collapse
no problem my friend
So anyways! I'm uploading the Mary v0.2 ROM now. It's all good. Hopefully it's a newer driver than the one that was originally in there.
Feedback anyone? Does it work properly on your Niki?
EDIT: That was stupid. I need to give you more upload links first!
Very nice indeed, feels like my dual is 1000 times faster now!!
Great job!
xangma said:
So anyways! I'm uploading the Mary v0.2 ROM now. It's all good. Hopefully it's a newer driver than the one that was originally in there.
Feedback anyone? Does it work properly on your Niki?
EDIT: That was stupid. I need to give you more upload links first!
Click to expand...
Click to collapse
Any sign of that link yet?
soulcrusher said:
Very nice indeed, feels like my dual is 1000 times faster now!!
Great job!
Click to expand...
Click to collapse
Really ???
Interesting..!
Could this great work from xangma (thank you btw) be useful to have Manila working om Niki?
Klutsh said:
Any sign of that link yet?
Click to expand...
Click to collapse
Yep, there is Going to do it separately on RapidShare in a second I think. That site is weird. Oh I get it. You have to wait their time limits to get the link. Open and wait.
Thanks for the link,
"You have exceeded your Download Quota!"
from Badongo.com, I've never used their site before!!
Grabbed from rapidshare instead.
OK, Mary Rom is a little bit faster but not 1000 times..
but thx for your work.
Blackdragon_860 said:
OK, Mary Rom is a little bit faster but not 1000 times..
but thx for your work.
Click to expand...
Click to collapse
=) Even a little is better until we get some new kaiser drivers =D That would be nice.
Has anyone tried the Niki Project version yet?
Blackdragon_860 said:
OK, Mary Rom is a little bit faster but not 1000 times..
but thx for your work.
Click to expand...
Click to collapse
I have to agree, only a slight improvment, I think now it's a case of waiting for the GPU drivers... and waiting... and waiting
no more faster for me
anyway i will look in it . Thanks xangma .
Else anything in future ?
{
"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"
}
just take some pictures video demo of microsoft.As u can see.In pictures.Ours niki device running WM7
So why we need change device ?
Will have something in next times for all !

[KITCHEN] Raphael Kitchen (From JugglerLKR and JCEspi2005)

Well, now that my Raphael is finally coming to me, i'm going to put my attention here...
Like in the Kaiser forum, this is a team work with JugglerLKR.
First of all, give thanks to all ppl that contribute to this kitchen (read first post), and all of you that help to make better with your feedback and suggestions...
This is a adaptation from KaiserKitchen to Diamond and Raphael. So don't wait an spectacular GUI, is as simple as the first version, a script with the tools needed in a folder. This way we can upgrade individual tool when needed...
This is the v0.6 (second version for Raphael). I have rewrited the script in a single file starting with the Alex's modification over the original batch files from version v0.3 for Kaiser. (many thanks Alex's for his works over the original script...)
UPDATE: Kitchen upgrade to resolv issues with reconstruction process. Now version 0.61 works fine.
UPDATE2: Kitchen upgrade to make a better extraction process. Now the XIP part is taked out of imgfs part before cook. Tested and verified to work fine with a shipped ROM and with a reconstructed one. Modified the tool IMGFSFROMDUMP.EXE to allow more than 128Mb imgfs partition size. Added XVI32 application to edit the NBH file and modify the PagePool according this thread http://forum.xda-developers.com/showthread.php?t=430345. Version 0.62 uploaded.
The kitchen have three basic steps, first you need extract a base ROM to modify. Second you need to modify the extracted content (easy cause is package organized). Third you need to cook the modifications you did. The result of the whole process is a NBH file you can flash with RaphaelCustomRUU (included in the ROM). Of course you need the HardSPL before do this (not indluded in the ROM, you can get here http://forum.xda-developers.com/showthread.php?t=410150)
Now all functions are in one menu...
{
"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"
}
The first option allows to extract the XIP and OS content from a ROM (shipped or dumped) and make packages to make easy the next step...
Next image show the extraction menu with shipped and dumped ROM
Once you get the content extracted, you will have a set of folders inside the kitchen like the next image...
OEM folder have the OEM part of the OS. ROM folder have the original OS.NB file and XIP extracted part. And SYS file have the SYS part of the OS.
Next step is to cook the ROM after you have introduced the modifications to the future ROM. Next imagen shows the cook menu when you can choose Bepe's BuildOS or Ervius one.
Once you have finished with the cook step, you can flash the NBH file you will have in the kitchen folder named RUU_Signed.NBH.
In the (m) More Options menu you have the cooking process step by step if you want to take more control over the process...
This are basics steps, so feel free to make any recomendation, suggestion or any other question related to the kitchen that allow us to make it better.
Links to the Kitchen:
http://rapidshare.com/files/146058925/Raphael_ROM_Kitchen_v0.6.rar
http://rapidshare.com/files/147092569/Raphael_ROM_Kitchen_v0.61.rar
http://rapidshare.com/files/151114881/Raphael_ROM_Kitchen_v0.62.rar
Mirror: http://www.4shared.com/file/67398870/5d504a33/Raphael_ROM_Kitchen_v062.html
Read the TXT file inside to get the pass.
Waiting your feedback, guys.... thanks...
Cheers.
Post Reserved
[UPDATE 18-sep-08] Raphael ROM Kitchen
Here goes "old fashioned" kitchen, functional as well as above one, you can choose the interface you want to use.
Raphael ROM Kitchen - "just in case" edition.
It is slightly modified and updated well known Diamond/Kaiser ROM Kitchen to work with Raphael.
First backup everything and read "!!!readmefirst!!!.txt".
Thanks goes to
bepe
cmonex
dark simpson
itsme
jcespi2005
jugglerlkr
mamaich
olipro
pof
tadzio
theblasphemer
udk
and many others I forgot to mention...
http://rapidshare.com/files/133787810/JugglerLKR_Raphael_ROM_Kitchen_v0.5.rar
mirror:
http://vidmes.com/xda/raphael/Kitchens/JugglerLKR/JugglerLKR_Raphael_ROM_Kitchen_v0.5.rar
thanx TehPenguin!
remember, you need to flash developer edition unsigned HardSPL first:
http://forum.xda-developers.com/showthread.php?t=410150
p.s.: please test this kitchen on real devices and leave some feedback
p.p.s.: customruu.exe in this kitchen reported false positive by some anitviruses
thanx mrvanx & walshieau for reporting it.
yes, though custom RUU "should" be fine
please test updated Raphael kitchen on real devices and leave some feedback. but remember, that you need unsigned developer edition HardSPL - look here:
http://forum.xda-developers.com/showthread.php?t=410150
and some base rom here:
http://forum.xda-developers.com/showthread.php?t=410305
The customRUU in this kitchen MIGHT show up in AVG as a trojan dropper. Got assurance it is ok however.
Pain in the arse is you gotta disable AVG if you wanna run it, URGH!
i can also confirm and backup MrVanx! the CustomRUU "drops" the files outside of the exe, which can be seen as a Trojan File Dropper for people using AVG.
thanx, updated first post (i don't use avg)
is this a ROM of Raphael or just RUU.thanx
kkjjkkk said:
is this a ROM of Raphael or just RUU.thanx
Click to expand...
Click to collapse
Its a ROM Kitchen, to help develop ROMs. You need a ROM build like the ones posted here or a dump of your current ROM to make it work.
Mirrored: http://vidmes.com/xda/raphael/Kitchens/JugglerLKR/JugglerLKR_Raphael_ROM_Kitchen_v0.5.rar
- Enjoy!
small request for the kitchen guru's...
Hi All,
I'm a kaiser user who will be switching to the raphael!!
I used to do some amateur cooking for my kaiser. Just some finetuning of the roms for my personal taste...
I used Alex's kitchen to do so:
http://wiki.xda-developers.com/inde...ROM Kitchen Tutorial#Gatheringx20.Ingredients
In this kitchen there is a package-tool and also some other small but easy tools like a embedded pagepool changer.
When you use the kitchen for cooking it uses all these tools one by one.
A real heaven for nOOp's like me....
Is it possible to edit this kitchen for raphael to do the same things like the package tool and so on?
Thanks in advance.....
Now waiting for that raphael (touch pro)
merten3000 - i will try to update it for touch pro when i got real device...
JugglerLKR said:
merten3000 - i will try to update it for touch pro when i got real device...
Click to expand...
Click to collapse
thnx man! Appreciate it!!
Sound great because i'm am also a noob with rom cooking but i'm very eager to learn rom cooking.
"JugglerLKR merten3000 - i will try to update it for touch pro when i got real device... "
zal eens kijken in hoeverre ik dat in t nederlands kan vertalen
I sinned, so if any one else gets a stock NL Device don't forget to Dump it first.
Already playing with this kitchen and extracted rom but luckily nothing to flash on.
Maybe it's also a good idea to start an OEM Repository fairly early on so that it is set up and well known, from start.
I know it's not completely on Topic, but it's good that there's a little "Stilte voor de Storm" (Silence before the storm) moment where most users taking peaks here, are mostly already familiar with XDA.
Noonski said:
I sinned, so if any one else gets a stock NL Device don't forget to Dump it first.
Already playing with this kitchen and extracted rom but luckily nothing to flash on.
Maybe it's also a good idea to start an OEM Repository fairly early on so that it is set up and well known, from start.
I know it's not completely on Topic, but it's good that there's a little "Stilte voor de Storm" (Silence before the storm) moment where most users taking peaks here, are mostly already familiar with XDA.
Click to expand...
Click to collapse
Noonski which manual for dumping a ROM is the best to use. I'm a noob here but want to learn the tricks of the trade. I've seen many manuals but i don't know which one to choose from.
I've been using this kitchen to play around with ROMs etc, and have found the RomMaster included has problems dumping some Raphael XIPs. I replaced it with an alternative RomMaster, but thought I'd say here so people know...
l3v5y said:
I've been using this kitchen to play around with ROMs etc, and have found the RomMaster included has problems dumping some Raphael XIPs. I replaced it with an alternative RomMaster, but thought I'd say here so people know...
Click to expand...
Click to collapse
Yep the first go i had with the kitchen I found issues with the XIP, everything else was fine.

Categories

Resources