Related
Hi, I'm preparing all you need to kook a italian rom by yourself...
in some minutes 1st part, with programs that you need to extract .nb files from .nbh, and reassemble .nbh as you like, how to dump a rom and how recompile it..
bye!!!
ok, the utilityes you need are:
*** all utilities are ready to download in the end of this post!!! ***
1) nbhtool_trin.rar
2) package_tool.rar
3) nbdumper.rar
4) bepe_kichen_trinity_ita_WM-6.1.rar
Code:
6.1 bepe_kitchen.rar
5) Flash_nbh.rar (included into kitchen!)
6) rgu to xml transform an rgu or a reg file into a provxml file!!
7) dsm patcher to update also the dsms files to respect the rom's os and build version
1) nbtool from dutty is usefull to decompile/recompile nbh , decompil enbh, choose nbh to decompile, you have 1 or more .nb files, windows.nb is that you need, the rom, you should find also:
radio.nb (radio)
first/second_splash.nb (the 2 images shown as splashscreens!!!)
ipl.nb (boot of trinity...)
spl.nb
and other that now I not remember...
................
to recompile the nbh file, just select that you need (os.nb, first.nb second.nb)
for my experiences, try first times only with os.nb, choose the file and compile the nbh files,your rom is ready to be flashed into device...
2) package tools analize the dumped os windows.nb and tell about sys and oem versions, more it creates packages of dumped rom, and insert all files into the 2 system directory "oem" and "sys" with button (menu) "build packages"
3) nbdumper from tadzio, it is the important tool togheter bepe kichen, with it you are able to dump "windows.nb"
put windows.nb into the folder, dos prompt and write:
nbdump windows.nb (then press enter...)
in few minutes you have inside also the directory named: windows.nb.dump, iside you can find all files that will be in rom on your device...
4) now open package tools by bepe, search this directory, and analize, after analizing, click on build packages...
after some time, you in "windows.nb.dump" directory have: sys and oem folders...
this is the real os...
now you neeedd xip directory...
copy windows.nb into the directory named:XIP_extract (that you can find in "bepe_kichen_trinity_ita" tool...
copy it into the directory, rename from windows.nb into "os.nb"
click on "Make_XIP.bat" and then you have "xip" folder...
copy xip folder into "rom" folder in of "bepe_kichen_trinity_ita", copy os.nb too into "rom" folder, so you have rom folder and inside:xip fiìolder and os.nb...
ok...
now, oem and sys folder obtained with package tools, copy them into "bepe_kichen_trinity_ita" tools, and you have:
oem, sys, tools, xip_extract and rom folders, and the exes...
now is ready...
you have to click on "buildos.exe" and the rom will be build, ok, now there is a new folder, "temp", now you have finished, only click on createrom.bat and in few seconds you can find into \temp\ folder a file named os-new.nb, this is the new rom, build .nbh with dutty nbtools, and can flash it on your device!!!
5) to flash put nbh created into folder:Flash_nbh, flash....
next, tools and howto: create extended_roms;create own splashscreens, adding own packages (the packages are additional programs... into I left yet 3/4 packages from mine!!).....
*******************************************************************
I must make all credits also to udK, that discovered with me the right way to kook roms...
and invite all people to make some dotations to him, for the hard work that he made to have a good italian rom to mount on our devices!!!
thanks friend...
*******************************************************************
I think is better to try with udk or lasagna roms to start, they are perfext and logically structured as bepe kichen wants!!!
bye!!!
****************************************************************************************
*
* P.S.: and finally I think that if you decide to use udk rom to make experiments, you have to donate him,
* and if uou want to use lasagna rom to learn to use bepe kichen, also you have to make donations to guybrush.
* they worked hard to translate the rom, you must donete to use theyr roms I think is the only think to do
* to tell them "thanks!!!", really...
*
****************************************************************************************
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
lesson 2:
how make own splashscreen!!!
just open an image or create one, with also paint;
make it 240x320 pixels, 240 in width, 320 in height...
save it as bmp, with 24 bits...
open it with nb_image_converter
convert to "nb"
save it as first and second.nb...
now, if you don't have windows.nb use dutty's nbtools to extract from rom, reuse nbtools to compile nbh, add
in os: windows.nb
in "first splash" the file first.nb
in "second splash" the file second.nb...
compile nbh file and flash into ppc, when you finish, you can see you freferred splash screens!!
next:
create a package and/or translate the exe/mui files in your language with resource hacker!!!
try to open an exe, or first a mui files if there is into the package!!
you can see:
icon (you are able to change it , but is not important for us!!)
dialog, you can move the object inside them, rename or translate strings and other...
string table, here you can change, translate in your language tje strings of mui/exe!!!
and other, but for modify translate this basts!!
see later!!! bye!!!
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
lesson 3:
for mui:
if you have traslated them, you have also to rename: exaple, if therer is amui xxx_409.mui, in english of couse, and you stranslated it into italian, you hace also to rename it by xxx_409.mui to xxx_410.mui!!!
and for italians mui you can use the ones from tynh wm6 Italian rom!!!
and also initflashfiles.dat must be traslate...:
and also rgu files:example:
string: "programs" must became "programmi"
string: "my pictures" must became "immagini"
etc.etc.
howto: CREATE A PACKAGE!!!
ok, download theese utility:
wince cab manager from here:
http://www.ocpsoftware.com/
(full funcional trial for 15 days!!!)
and my utility: packages creator (a little tools of mine!! )
from here:
-------------------------------------------------------------------------------
UPPED:
(new version... bugs solved... option improved!!!)
now in bilingual ITA/ENG, and with more option to personalyze your new packages!!
new beta with more and more options to create initflashfiles.txt...
flag:"simulate folder names" on wince cab manager and put reg file into package folder you choice...
example: "...\trypackage\windows\batterystatus\batterystatus.exe"
you have to put reg file into "...\trypackage\to-import.reg" ok???
and here the new beta of package creator!!!
Hi all, from a Bennec83's Idea I released this last version that works with cab analyzer, and make packages from cab files automatically...
*******************************Re-reupped 1st good working release!!! 4.1 *********************
-------------------------------------------------------------------------------
ok!!!!
P.S.: if th bepe kichen shows an error during the kook operation, it will be becouse there is another file (duplicate file) yet present in rom, delete it from other subfolder, not in the package just inserted...
next appointmant to create own extended_rom!!! and some triks on registry (modifing rgu files!!!)
see you!!!
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
lesson 4 playing with extended rom:
howto: create and use extended roms...
ok, have to download the utility htc_extended_rom_editor
I think is all.... (for now!!!)
your knowledge about roms, its components, how to dump, build, add packages are full... rests to edit rgu and provxml...
but in next days....
bye bey and good experiments!!!
*********************************************************************************
*********************************** ******************************
*********************************** UPDATES ******************************
new version of buildos+packagetools, some imporvements, and context menu on packages to enable/disable them by default!!
new version of buildos, now:
1) xip porting for os ber updating;
2) updater for Rom Creation Date;
3) Updater for Rom version at Boot screen!!!
enjoy!!!
improved some context menus on selected package.....
xip porting for OS version and Rom's Date creations Updater!!
new version of package creator, to have own directory where place shortcuts, and some minor bugs solved
here: and added links in initflashfiles.txt for .htm files for "Help"!!!
P.S.: I need beta testing for my apps, becouse, I go on programming and there are allwais same bung into...
bye!!! ( a big thanks to guybrush and udk for testing and support, but specially to Vibranze for testing package creator!!!)
*********************************************************************************
Traduzione in italiano della guida del Kitchen
Lavori in corso..
ervius said:
Hi, I'm preparing all you need to kook a italian rom by yourself...
in some minutes 1st part, with programs that you need to extract .nb files from .nbh, and reassemble .nbh as you like, how to dump a rom and how recompile it..
bye!!!
Click to expand...
Click to collapse
thanx, let's start cook togheter
--reserved for packages--
I only hope that my 3d iwill be usefull to be better, and share togheter a lot of packages for our trinity devices!!
see lather...
I love you.
This is what I searched for long time.
Two question.
1) What difference there is between this and Orginiale Bepe ROM kitchen form Hermes.
2) Can I use all ROM that i Want to start the cooking?
....
3) This is possible some mirror not rapidshare? (for example www.divshare.com)
Grazie mille.
Viva il P3600.
cicciocant said:
I love you.
This is what I searched for long time.
Two question.
1) What difference there is between this and Orginiale Bepe ROM kitchen form Hermes.
2) Can I use all ROM that i Want to start the cooking?
Grazie mille.
Viva il P3600.
Click to expand...
Click to collapse
1) infinite greetings to bepe for the beautifull tool...
the kichen is the same, only you have os and xip for trinity (after you extrapolated oem-sys folders and xip!!!)
2) you can use all roms you want, also in other languages, but only if they , after you dumped and analyzed with bepe package tools, and have oem and sys folders (and xip folder...), but if you try with roms that have missed files, you must try to insert them into oem or sys dolder, you, after use bepe package tools must see only "oem" and "sys" folder, nothing else, to know that the rom is really ok..., in other case the rom was built in confused mode or with other utilities, that I consider oldier...
bye!!!
and my final point is also share a lot of packages....
for now I think it's all, but in few days I explain also howto build packages and other....
see you!!
ervius, very good tutorial i think it'll be useful not only for italian people but for everyone who want learn how to cook their own rom. Just a tip...be careful, read everything and try to understand how these tools works and check everything before try to flash your device.
Guybrush said:
ervius, very good tutorial i think it'll be useful not only for italian people but for everyone who want learn how to cook their own rom. Just a tip...be careful, read everything and try to understand how these tools works and check everything before try to flash your device.
Click to expand...
Click to collapse
yes... by attentions, use the tools at own risk, and specially use them with "brain"!!!
bye!!
Thanks ervius! you are truly "mythical". I`ll read all with much attention tomorrow, now i`m seat in one park bench to 5 meters from the sea.....
Hi...... morf3o.
added lesson 2 (how to create/modify images and create your splashscreens at ppc boot!!!)
at first post!!
see you later to build our first package!!!
I tried this tools with Lasagna 205 ROM.
I arrived to package tools
When I press "Build Packages" I've this error:
Code:
Syntax error map.txt:
tom
tom is the last lin of map.txt.
Can i delete it witouth problem?
At the end I've also the OEM and SYS directory but there are also three file out all directory:
Recorder.exe
Voice Recorder (link)
Recorder.exe.0410.mui
It's ok?
One Advice.
To arrive at DUMP directory and afther to OEM and SYS I found more easy and fast this way:
http://forum.xda-developers.com/showthread.php?t=316940
Thanks 1000!
cicciocant said:
I tried this tools with Lasagna 205 ROM.
I arrived to package tools
When I press "Build Packages" I've this error:
Code:
Syntax error map.txt:
tom
tom is the last lin of map.txt.
Can i delete it witouth problem?
At the end I've also the OEM and SYS directory but there are also three file out all directory:
Recorder.exe
Voice Recorder (link)
Recorder.exe.0410.mui
It's ok?
One Advice.
To arrive at DUMP directory and afther to OEM and SYS I found more easy and fast this way:
http://forum.xda-developers.com/showthread.php?t=316940
Thanks 1000!
Click to expand...
Click to collapse
so, you have to install also java virtual machine... with this utilities in not necessary...
thanks ciccio but i'd like to continue with bepe's kichen, do you like use it??
ok...
3 files are out, put them into \oem\oemapps\ directory, so you now have only oem and sys directory, then... extract xip etc... etc...
ok!!!
thank's for your answers.
I like also Bepe's Kitchen. GO ON!
For the Syntyax error?
I've to delete "tom" at the end of map.txt?
cicciocant said:
thank's for your answers.
I like also Bepe's Kitchen. GO ON!
For the Syntyax error?
I've to delete "tom" at the end of map.txt?
Click to expand...
Click to collapse
I don't have your error, but if finally you have oem and sys folders, then it works well...
but you can try to delete and post if it work...
bye!!
Sorry for my newbie question...
In my understanding all this tools are working with ROM files you already found "somewhere".
What I want to do first is getting a working ROM out of a Trinty device. E.g. I have a german Vodafone device with the Vodafone custom ROM. I simply want to "copy" this ROM on my Harddisk. No changes. I only want to be able to flash it back if I want to, to have the device in the same state it is now.
Which tool do I have to use?
What do I have to do?
Check this article
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
Ciao
A question ervius:
we suppose that I succeed to modify/create my first ROM, exists a way in order to test it without flash on my device? A way for being sure that if I flash, i do not burn my trinity....
Thanks........ morf3o.
morf3o said:
exists a way in order to test it
Click to expand...
Click to collapse
The only way is flash your trinity and hope
claros said:
Check this article
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
Ciao
Click to expand...
Click to collapse
Thanks... that is what I was looking for. I found this (http://www.modaco.com/Paul-s-guide-to-backin-t255090.html) in the meantime. But the two guides differ: Paul says, that I only need the Part02.raw file. Why?
saminegm said:
Thanks... that is what I was looking for. I found this (http://www.modaco.com/Paul-s-guide-to-backin-t255090.html) in the meantime. But the two guides differ: Paul says, that I only need the Part02.raw file. Why?
Click to expand...
Click to collapse
Your OS is in part2, first two parts are the XIP partition aka your boot sector.
Ciao
Hi , last version of buildos+package tools....
try 4.2b3 version now.....
Last version 29.04.2008
http://rapidshare.com/files/111296473/kitchen.zip
improved real xipporting with buildxip.exe...
how it works...
dump xip.bin from same or other device; so you have xip\ folder annd romhdr.bin.
copy xip\ folder just created into my buildos by clicking on:"New Xip"
and then by pressing on: "port it" and selecting all xip->same or different device xip, you finally have new xip build ported into my kitchen, ready to be builded into "out.bin" by buildxip executed by all "CREATE_ROM_xxx.bat" files building new rom.
Code:
this last version has also load/save config, so you can preconfigure from
ultralight to full rom, load a config file and only by a click you have the
preferred rom to build, so you can publish in a bit all kind of roms you want!!!
this tool goes into kitchen or bepe's WM 6.1 one, or WM 6.1 of mine...
try it and post new bat and \TOOLS utils to extrac xip from other devices to make better it..
and also bat and \TOOLS utils to extract os.nb from other devices....
(I think the bats have to named like: "EXTRACT_DUMP.......bat" example: Extract_dump_from_kaiser; extract_Dump_from_hermes ecc... )
ervius said:
Hi , last version of buildos+package tools....
added:
to extract xip for non trinity roms, at dump\ analyzing... it execute a bat file...
all bat files to extract xip are stored into \TOOLS folder, and must have a name that starts with: "XIP_extract" example: XIP_extract_From_hermes.bat; XIP_extract_from_trinity.bat ecc....
try it... obviously there are a lot of devices, you can try for yours and post the bat to make bettere xip extracting of buildos , inside \tools folder, yet XIP_extract_from trinity.bat and XIP_extract_from_kaiser.bat
TODO:
extract from os.nb by other devices from executing others bat like xip extracting...
bye!
download here:
http://rapidshare.com/files/103757462/buildos_3.9b3.rar
try it and post new bat and \TOOLS utils to extrac xip from other devices to make better it..
and also bat and \TOOLS utils to extract os.nb from other devices....
(I think the bats have to named like: "EXTRACT_DUMP.......bat" example: Extract_dump_from_kaiser; extract_Dump_from_hermes ecc... )
Click to expand...
Click to collapse
Can you give us a description of your cooking?
cyron_at said:
Can you give us a description of your cooking?
Click to expand...
Click to collapse
to dump an nb file....
it need \dump folder and os.nb
outside folder.... open package tools.... and can rebuild oem\ and sys\
if you want you can insert also \xip folder using inside \tools bats....
choicing what device is from the os.nb and choice the right bat included, listed into a form with a max of 16 radiobutton to choice bat....
to build rom:
only open buildos choice rom dumped (oem\ sys\ xip\)
and it rebuild \dump folder, then, by executing a bat (that you can change to your use (also this can be implemented: more bats to have multidevices rombuilder....) and finally you have new os.nb or executing also ruu_updates_rom, the windoe to flash new ruu_signed).....
bye!
ervius said:
to dump an nb file....
it need \dump folder and os.nb
outside folder.... open package tools.... and can rebuild oem\ and sys\
if you want you can insert also \xip folder using inside \tools bats....
choicing what device is from the os.nb and choice the right bat included, listed into a form with a max of 16 radiobutton to choice bat....
to build rom:
only open buildos choice rom dumped (oem\ sys\ xip\)
and it rebuild \dump folder, then, by executing a bat (that you can change to your use (also this can be implemented: more bats to have multidevices rombuilder....) and finally you have new os.nb or executing also ruu_updates_rom, the windoe to flash new ruu_signed).....
bye!
Click to expand...
Click to collapse
...it need \dump folder and os.nb
-> which means I should extract rom?
--> How can I do this?
---> I am using the tools of RomDonald. Is this ok?
From the tool:
1.) Open: There I select my \Dump\folder
2.) How can I rebuild oem/sys?
Questions over questions...
Would you be so kind and make a few screen-shots?
I would be veryyyyyy happy!
Thx,
Chris
cyron_at said:
...it need \dump folder and os.nb
-> which means I should extract rom?
--> How can I do this?
---> I am using the tools of RomDonald. Is this ok?
From the tool:
1.) Open: There I select my \Dump\folder
2.) How can I rebuild oem/sys?
Questions over questions...
Would you be so kind and make a few screen-shots?
I would be veryyyyyy happy!
Thx,
Chris
Click to expand...
Click to collapse
read also this 3d...
http://forum.xda-developers.com/showthread.php?t=320504
Once XIP is extracted, what exactly gets done to port the XIP to trinity?
Thank ERVIUS
Very good tools ...
4.0b1 is borning, what about???
now:
1) it can dump os.nb from different devices (kaiser / hermes/trinity for now!) executing differents bat made just to dump them...
2) extract xip from different devices (kaiser/hermes/trinity for now!) by executing different bats made just to extract them...
3) build os (for trinity/hermews also ruu_signed.nbh) for different devices (kaiser/hermes/trinity for now)
I think tomorrow, ops today in the afternoon, I'll post it....
what I need???
that someone make some bats to dump/build os.nb for other devices, and bats to extract xip from other devices....
bye!!!
Build Packages,..
Hello!
There is an "error" while building packages:
When I say: Do not import XIP..-> There is no XIP folder in the rom -> Load rom does not work
When I say yes & import from trinty there is an error message :-(
However the XIP folder will be created. But the boot.rgu ... is not the boot.rgu from the origial rom. What must I do now?????
Any idea?
Thx
cyron_at said:
Hello!
There is an "error" while building packages:
When I say: Do not import XIP..-> There is no XIP folder in the rom -> Load rom does not work
When I say yes & import from trinty there is an error message :-(
However the XIP folder will be created. But the boot.rgu ... is not the boot.rgu from the origial rom. What must I do now?????
Any idea?
Thx
Click to expand...
Click to collapse
yes, wait the 4.0b1....
and test that one....
ervius said:
yes, wait the 4.0b1....
and test that one....
Click to expand...
Click to collapse
Sure! When do you think will the release be published?
cyron_at said:
Sure! When do you think will the release be published?
Click to expand...
Click to collapse
some minutes, I'm upping 19209 Italian kitchen that contains buildos-packagetools 4.0b1!!!
ervius said:
some minutes, I'm upping 19209 Italian kitchen that contains buildos-packagetools 4.0b1!!!
Click to expand...
Click to collapse
Thanks Ervius... Great News!!! i will test it tonight.
axl79 said:
Thanks Ervius... Great News!!! i will test it tonight.
Click to expand...
Click to collapse
yes...
if I'll able to upload it....
some connectivity problems.....
buildos is online.... version 4.0b2.....
to insert imto kitchen...
bye!
ervius said:
buildos is online.... version 4.0b2.....
to insert imto kitchen...
bye!
Click to expand...
Click to collapse
added v2 version of 4.0b1, some bugs solved on CREATE_ROM_***.bat executing...
ervius said:
added v2 version of 4.0b1, some bugs solved on CREATE_ROM_***.bat executing...
Click to expand...
Click to collapse
Thank you.. Really nice tool! Trying tonight!
hey ervius I can use this tools to build a 19209 rom? Are you going to release your versions?
GDT said:
hey ervius I can use this tools to build a 19209 rom? Are you going to release your versions?
Click to expand...
Click to collapse
yes, you can, I posted kitchen until this afternoon, and don't know if I'll post the 19209 rom...
version 3 in 1st post...
some improvements, soved other little bugs, added "execute CREATE_ROM_***.bat" flag by default and context menu to delete files on "search duplicete files" into rgu editor...
bye!
Hi every gurus and chefs,
Thanks to creators of kitchens and tools, i have had so much fun in cooking my own rom. Thank you so much.
Recently, i tried to convert the 1.93.456.2 WWE ROM to CHS. I have managed to transform 99% of the ROM into CHS. but there is only one problem. When creating the rom using the diamond kitchen or kaiser kitchen, at the ending part, it will fall back to use os.nb within the ROM\ folder.
From my understanding, the OS.NB file is an extracted OS from the original WWE ROM thus, the boot.hv, boot.rgu and wince.nls is still the WWE version. how do I replace these files?
Another question would be, when dumping the official rom, the dump_XIP folder is created. what is the use of this folder? if i make changes to the folder, how to i merge them into a usable part for cooking?
i have did a lot of reading on XIP porting, big storage rom cooking and etc. i just can't seems to locate one which explains how to replace files in os.nb or merging the XIP folder to usable part.
Can any kind soul please kindly advise?
Thanks you so much!
You may want to have a look at ababrekars SYS and XIP porting guide in Elf section....
ruffruff said:
Hi every gurus and chefs,
Thanks to creators of kitchens and tools, i have had so much fun in cooking my own rom. Thank you so much.
Recently, i tried to convert the 1.93.456.2 WWE ROM to CHS. I have managed to transform 99% of the ROM into CHS. but there is only one problem. When creating the rom using the diamond kitchen or kaiser kitchen, at the ending part, it will fall back to use os.nb within the ROM\ folder.
From my understanding, the OS.NB file is an extracted OS from the original WWE ROM thus, the boot.hv, boot.rgu and wince.nls is still the WWE version. how do I replace these files?
Another question would be, when dumping the official rom, the dump_XIP folder is created. what is the use of this folder? if i make changes to the folder, how to i merge them into a usable part for cooking?
i have did a lot of reading on XIP porting, big storage rom cooking and etc. i just can't seems to locate one which explains how to replace files in os.nb or merging the XIP folder to usable part.
Can any kind soul please kindly advise?
Thanks you so much!
Click to expand...
Click to collapse
Hi,
1. You don't have to replace/port XIP from the ROM of the same device. Only do this if you want to port other devices' ROMs such as Kaiser to Hermes, Diamond to Kaiser, Raphael to Diamond etc. It will boot.
2. Just replace the wince.nls version in the SYS\WINCENLS_WWE with the CHS one you have.
3. Modify all the MUI files and registry as to point to your Language of choice.
4. The OS.NB is needed as the shell/container for your new cooked ROM because it's the requirement for using the Tadzio's tools. So, leave it as is.
5. Cook the ROM.
At least that what I did when doing my Hermes version long before.
Cyphol.
ruffruff said:
Hi every gurus and chefs,
Thanks to creators of kitchens and tools, i have had so much fun in cooking my own rom. Thank you so much.
Recently, i tried to convert the 1.93.456.2 WWE ROM to CHS. I have managed to transform 99% of the ROM into CHS. but there is only one problem. When creating the rom using the diamond kitchen or kaiser kitchen, at the ending part, it will fall back to use os.nb within the ROM\ folder.
From my understanding, the OS.NB file is an extracted OS from the original WWE ROM thus, the boot.hv, boot.rgu and wince.nls is still the WWE version. how do I replace these files?
Another question would be, when dumping the official rom, the dump_XIP folder is created. what is the use of this folder? if i make changes to the folder, how to i merge them into a usable part for cooking?
i have did a lot of reading on XIP porting, big storage rom cooking and etc. i just can't seems to locate one which explains how to replace files in os.nb or merging the XIP folder to usable part.
Can any kind soul please kindly advise?
Thanks you so much!
Click to expand...
Click to collapse
please correct me if i was wrong..
afaik, XIP part is the same for every language,
also in the end part of the building, you need os.nb only as a "template" to rebuild the new one... it wasn't really use the content inside...
normally, you need to copy all content in the dump_xip to the ROM\XIP directory...
to learn about the process of diamond kitchen (which is based on kaiser kitchen so i assume the tools are the same), i think you better use the kaiser ROM, and try to dump it.. and see what directories and files are generated...
in kaiser kitchen, to rebuild the rom you need 3 dirs, OEM, SYS, and ROM\XIP
cyphol said:
Hi,
1. You don't have to replace/port XIP from the ROM of the same device. Only do this if you want to port other devices' ROMs such as Kaiser to Hermes, Diamond to Kaiser, Raphael to Diamond etc. It will boot.
Click to expand...
Click to collapse
He would need to if he wants a different OS build. Or am I wrong?
pkoper said:
He would need to if he wants a different OS build. Or am I wrong?
Click to expand...
Click to collapse
of course....
pkoper said:
He would need to if he wants a different OS build. Or am I wrong?
Click to expand...
Click to collapse
Yes, that's right for the reason. If that's the only reason, why don't you replace the core.dll
thank you everyone for your advise.
looks like i just need more reading.
thank you cyphol, pkoper and teamee for your kind advice.
I have replace the SYS\wincenls_WWE folder with SYS\WINCENLS_0804. i believe this might be one of the problems. i will try replacing just the wince.nls within the folder instead of replacing the entire folder.
files which i have modified includes the boot.hv, user.hv, default.hv, boot.rgu, a bunch of other rgu as well. i might have missed out a few others. so i will check again.
thanks everyone for your kind advice. if there is any other suggestions or points to take note of, please kindly let me know.
your guys rocks! XDA rocks!
Can Sombody Please Post a clean fast rom in OEM and SYS folder format, so that it is ready for cooking with as i cannot seem to find one that will extract with core's kitchen, all i can get to extract is the t-mobile ofical rom and this is far from clean
YuE v10 or v11 would be a good choice.
i second this, urgently - a plea to all cooks!!!
greetz
well i dumped the extraclean 10 but still i'm figuring out how to modify it
any advise?
y_bother said:
well i dumped the extraclean 10 but still i'm figuring out how to modify it
any advise?
Click to expand...
Click to collapse
I now trying to collect it all ;-)
Here is the tools, RRU and BuildRom.bat with Empty SYS OEM and ROM folders foryou chefs to fill with food needed to build a clean rom if this is of any help for testing purposes
http://rapidshare.com/files/149197230/Sys_Oem_Empty.rar.html
sleurhut said:
I now trying to collect it all ;-)
Click to expand...
Click to collapse
Please let us know how to do it when you have worked it out.
I have tried and when i came to build I just got errors with XIP and i also had missing files, os.nb.payload romhdr.bin
solved the os.nb.payload by renaming os.nb to os.nb.payload
copied the romhd.bin from artemis_diamondish
XIP errors with
Code:
BUILDXIP 0.54 Copyright (c) 2007-2008 bepe 30 Jan 2008
ERROR: "XIP" dose not exist or it dose not contain any Modules!
I used extract xip in the core's kitchen and xip is in the ROM folder
Any ideas?
OK So now I just Copied XIP from Artemis_Diamondish and the rom builds
so how do i get the correct XIP For this Rom?
EDIT:
This plan didn't work
Anyone managed this yet
thanks
I'm trying to port my Asus P565 (XDA Zest) to WM6.5. This is my first attempt at cooking a ROM and I'm a little stuck - I just can't get the device to boot after flashing.
These are the steps I have done so far:
1. Used p835abisplit2 to extract Original WM6.1 P565 ABI into os.nb0
2. Extracted XIP from os.nb0
3. Extracted imgfs dump from hdubli's 21231 ROM
4. Ported XIP using XIP Kitchen, original XIP as Device XIP, 23022 as Donor XIP & hdubli's 21231 .VM & .ROM folders
5. Padded XIP to original size using bPatch.exe
6. Copied SYS from 23022 into Vivi's P252 kitchen & rebuilt using BuildOS
7. Created imgfs.bin from dump folder
8. Merged XIP.bin back into os.nb0
9. Merged imgfs.bin back into os.nb0
10. Converted to .abi & flashed to device
And I can't get it to boot no matter what. As I said, I'm a n00b to cooking ROMs, so if someone could point out where I'm going wrong I would be eternally grateful!
Blade0rz said:
I'm trying to port my Asus P565 (XDA Zest) to WM6.5. This is my first attempt at cooking a ROM and I'm a little stuck - I just can't get the device to boot after flashing.
These are the steps I have done so far:
1. Used p835abisplit2 to extract Original WM6.1 P565 ABI into os.nb0
2. Extracted XIP from os.nb0
3. Extracted imgfs dump from hdubli's 21231 ROM
4. Ported XIP using XIP Kitchen, original XIP as Device XIP, 23022 as Donor XIP & hdubli's 21231 .VM & .ROM folders
5. Padded XIP to original size using bPatch.exe
6. Copied SYS from 23022 into Vivi's P252 kitchen & rebuilt using BuildOS
7. Created imgfs.bin from dump folder
8. Merged XIP.bin back into os.nb0
9. Merged imgfs.bin back into os.nb0
10. Converted to .abi & flashed to device
And I can't get it to boot no matter what. As I said, I'm a n00b to cooking ROMs, so if someone could point out where I'm going wrong I would be eternally grateful!
Click to expand...
Click to collapse
Use the original 6.1 abi to get OEM and SYS
USe the OEM and use 6.5 SYS from the builds here
Use the scripts which I have mentioned
u can get ROm to boot
hdubli said:
Use the original 6.1 abi to get OEM and SYS
USe the OEM and use 6.5 SYS from the builds here
Use the scripts which I have mentioned
u can get ROm to boot
Click to expand...
Click to collapse
What about P552w? Are the step same as P565?
And How to add the language packages into the list?
Because, It's not suitable to use ervius Kitchen to process Asus ROM
Oh, where could I get the hdubli's scripts?
Moreover... May I know the minimum file list in OEMMISC for making cleaner ROM?
i.e. without Youtube&Flickr, ClearVue PDF Viewer, Asus Today, Asus Launch!, EziMusic, EziPhoto and StreamingPlayer
I have copied OEM packages from 6.1 ROM & SYS from 6.5 ROM into Kitchen & built OS. Still nothing. Do I need to copy anything from new/old XIP into kitchen? Does anything else need to be done to XIP after I port it via XIP Kitchen? I took out hd.dll, osaxst0.dll, mencfilt.dll and cachefilt.dll as there wasn't enough space in the XIP - does this matter?
Also, I am using the .VM file from your ROM for G'Reloc.
I think I'm missing one crucial step somewhere
Nagato - I think P552w should be the same process, only using different SYS DPI. For languages you need the appropriate SYS files for your language from Da_G's thread here:
http://forum.xda-developers.com/showthread.php?t=544445
(See also Post #4 for how to integrate these)
The tools used are:
p835abisplit2.exe - To extract os.nb0 from .abi
osnbtool.exe - To extract IMGFS, XIP & ExtROM from os.nb0
XIP Kitchen - To port 6.1 XIP to 6.5