http://bbs.xbeta.cn/viewthread.php?tid=30934&extra=&page=1
http://www.dbank.com/download.action?t=40&k=MTg5NzA5MA==&pcode=LCw1MTA1MCw1MTA1MA==
XIP.BIN
http://www.dbank.com/download.action?t=40&k=MTg1MDEwMA==&pcode=LCw1MTA1MCw1MTA1MA==
HTC_Messaging_Client_1_15_19211631_01
http://bbs.xbeta.cn/thread-31039-1-1.html
http://www.dbank.com/download.action?t=40&k=MTkwODk2Ng==&pcode=LCw2MDQwOCw2MDQwOA==
someone must explain if the XIPs must be modified before preparing the kitchen
Thank you _X_. Already ported it and now testing.
For some reason confused:Newbie) i did it only with a 23088 rom. Thanks again
28004 Just released today... Dang, these keep coming too fast.
http://forum.xda-developers.com/showpost.php?p=5008672&postcount=8457
Does somebody have the answer to matlegro's question? I've been wondering the same thing. So far, the ones I've downloaded have worked as is, but 28002 didn't seem to.
28004 also here:
http://bbs.xbeta.cn/thread-24444-1-1.html
^with more language options^
0409 ENG: http://www.rayfile.com/files/aeb40ae8-d864-11de-a59a-0014221b798a/
DPI and RESV: http://www.rayfile.com/files/45f3a4bd-d864-11de-b43e-0014221b798a/
also found this:
- http://bbs.xbeta.cn/thread-31101-1-1.html
guess this is chome M2D with link to QVGA - link that starts with Q?
- also few more QVGA OEMs:
http://bbs.xbeta.cn/thread-25109-1-1.html
SuperSport said:
28004 Just released today... Dang, these keep coming too fast.
http://forum.xda-developers.com/showpost.php?p=5008672&postcount=8457
Does somebody have the answer to matlegro's question? I've been wondering the same thing. So far, the ones I've downloaded have worked as is, but 28002 didn't seem to.
Click to expand...
Click to collapse
Hi SuperSpot
Like i said i have port the 28002 rom but only with a 23088 rom.
Until now is working, stable and very fast.
I don't know if is the right way to do that (or what i'm doing) but i use the xip tool in the ervius kitchen and it works.
The only problem is that we have only the xip without the sys, so the rom version appears SO CE 5.2.28002 (COMPILATION 23088.5.3.0). I don't know if i'm saying some bull****.
I will test the 28004 today.
Thanks again _X_.
P3P2000 said:
Hi SuperSpot
Like i said i have port the 28002 rom but only with a 23088 rom.
Until now is working, stable and very fast.
I don't know if is the right way to do that (or what i'm doing) but i use the xip tool in the ervius kitchen and it works.
The only problem is that we have only the xip without the sys, so the rom version appears SO CE 5.2.28002 (COMPILATION 23088.5.3.0). I don't know if i'm saying some bull****.
I will test the 28004 today.
Thanks again _X_.
Click to expand...
Click to collapse
would excuse, explain me the procedure?
matlegro said:
would excuse, explain me the procedure?
Click to expand...
Click to collapse
What i did was:
1) open the ervius kitchen, in this case with a 23088 rom.
2) hit on xipporterex & rom tool (button on the left side).
3) we have to say where is the old xip and the new one, so I hit on "..." (near de old xip folder button) and told the way where is the old xip (rom/trinity/xip.bin). It gonna ask if we accept the overwrite cause is already there. I say yes.
4) the same procedure but now for the new xip. Hit "..." and say where is your new xip.bin file. Again the thing about the overwrite, bla bla bla bla ,and hit yes.
5) next i hit the box "is as AKU-5"XIP" !!! (WM6.5)
6) Removed the "v" on the box "Execute Cert Patcher!) because I didn't have a Cert Patcher for this Rom. I think is the time killer.
7) Removed de PP Patcher, again i don't have one of this and i don't know is for about
8) hit box "change PP to mb" and change it to 4 mb. (PagePool)
9) Next and last hit "Port IT!!!"
Wait a few moments and voilá...
Like i said, i don't know if is the right way to do, but it works for me.
Regards
P3P2000 said:
What i did was:
1) open the ervius kitchen, in this case with a 23088 rom.
2) hit on xipporterex & rom tool (button on the left side).
3) we have to say where is the old xip and the new one, so I hit on "..." (near de old xip folder button) and told the way where is the old xip (rom/trinity/xip.bin). It gonna ask if we accept the overwrite cause is already there. I say yes.
4) the same procedure but now for the new xip. Hit "..." and say where is your new xip.bin file. Again the thing about the overwrite, bla bla bla bla ,and hit yes.
5) next i hit the box "is as AKU-5"XIP" !!! (WM6.5)
6) Removed the "v" on the box "Execute Cert Patcher!) because I didn't have a Cert Patcher for this Rom. I think is the time killer.
7) Removed de PP Patcher, again i don't have one of this and i don't know is for about
8) hit box "change PP to mb" and change it to 4 mb. (PagePool)
9) Next and last hit "Port IT!!!"
Wait a few moments and voilá...
Like i said, i don't know if is the right way to do, but it works for me.
Regards
Click to expand...
Click to collapse
when I perform "Port it!!!", me from the following errors:
1) Error executing: dumpxip.bat for old xip.bat!
2) Error executing: dumpxip.bat for new xip.bat!
3) boot.rgu in xip.bin_old not found! Create new... but maybe rom will be NON BOOTABLE!
4) Error executing: boot.bat!
Please, why?
matlegro said:
when I perform "Port it!!!", me from the following errors:
1) Error executing: dumpxip.bat for old xip.bat!
2) Error executing: dumpxip.bat for new xip.bat!
3) boot.rgu in xip.bin_old not found! Create new... but maybe rom will be NON BOOTABLE!
4) Error executing: boot.bat!
Please, why?
Click to expand...
Click to collapse
Yes I know. It happened with me when I try following the same steps but with de 28004 xip. Try the 28002 instead. Like i said, 28002 with me works well.
When this happends we have to make the procedure manually.
Please see posts at:
http://forum.xda-developers.com/showthread.php?p=4898916
and
http://forum.xda-developers.com/showthread.php?t=438676
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
last Rom: 3.07 with last OS 5.2.19209 build 19209 aku 1.0.2
a BIG thanks to: bepe: for all!!!...
and...
cmonex: for guide about have no more signed file check (you can cange system files into \windows on the fly in your ppc!!!)
and...
ausdin: for xip part to solve mail iusses (only for some devices...)
and...
eliasweb: for fixes like: autohibernate, processkiller, actsynckiller and other...
and...
adewidt: for dll replacing to solve A2DP iusses caused by previous xip part replacement...
what inside:
some screenshots...
download here:
http://rapidshare.com/files/105803486/ervius_3_07_WM6_1_ITA_essential__build_19209_.zip
if you want is better first of all (but not necessary!) install DES Hard SPL:
http://rapidshare.com/files/97120933/DES_Hard-SPL.TRIN_2.zip
SERIAL NEED???
here the licenser, so you can use it like you want and disable the nag screen...
(you have to install this cab on the Device and execute it... )
http://rapidshare.com/files/102451818/Rom_Licenser.cab
P.S.:
for Hard spl, sip selector and sdconfig tool here:
http://forum.xda-developers.com/showthread.php?t=379704
bye!
Great ervius!
I'm waiting for the link...
Thanks again and again and again...
Bye
ivansc said:
Great ervius!
I'm waiting for the link...
Thanks again and again and again...
Bye
Click to expand...
Click to collapse
1 second of bad connectivity, costs another half an hour to upload it....
damn....
Great Ervius
In the screenshot the build is 19202 and not 19209...
tank's ervius .... without the cube it could be great
zooster said:
In the screenshot the build is 19202 and not 19209...
Click to expand...
Click to collapse
yes, I used the previous, but is 19209, shure....
great work ervius!!!
tnx
marcosorano said:
tank's ervius .... without the cube it could be great
Click to expand...
Click to collapse
the cube is sleeping into it....
if you don't enable, it doesn't works, and can delete also lnk into "esecuzione automatica" folder...
I tell you witch .lnk files have to delete, then!
ADDED Download link!!
bye!
yas but it take 10 mb of memory
Ervius,
it's time to make it clear: why don't you just remove all the previous versions and say "ok, flash this one", there are too many ROMs by you around, it's very difficult to choose between all of them
ervius...thanks for all!!! you are great and your work is OUTSTANDING!!!
only a little help for your future works...why don't you try to open a single post of new relases where you put the link of various version (essential plus, essential minus, etc.etc)?
in this way...i think your works would be more appreciated due to more visibility of thread!!
and last but not least...can u try to relase this ROM version with essential minus as previous one???
thanks again
3.07
on htc home it doesn't show the music player tab
Great Ervius, you are number one!! I test it immediatly...
marcosorano said:
on htc home it doesn't show the music player tab
Click to expand...
Click to collapse
the version 2.1 don't have it.
vysus said:
Ervius,
it's time to make it clear: why don't you just remove all the previous versions and say "ok, flash this one", there are too many ROMs by you around, it's very difficult to choose between all of them
Click to expand...
Click to collapse
I think if you read the 1st post of any 3d, you understand what kind of rom you want or need.
marcosorano said:
yas but it take 10 mb of memory
Click to expand...
Click to collapse
if you want you can remove it from rom....
open a frouchflo.cab that have all inside (or see the ones present in my 19202 kitchen)
dump the rom, delete all files, delete all occurrences into initflashfiles.dat
and rebuild rom without it.
this could be a good solution.
ervius said:
if you want you can remove it from rom....
open a frouchflo.cab that have all inside (or see the ones present in my 19202 kitchen)
dump the rom, delete all files, delete all occurrences into initflashfiles.dat
and rebuild rom without it.
this could be a good solution.
Click to expand...
Click to collapse
::k not possible for me to do that... one more question, in htc home
doesn't appear music player tab what can i do for that without dump and recompile your fantastic rom?
marcosorano said:
::k not possible for me to do that... one more question, in htc home
doesn't appear music player tab what can i do for that without dump and recompile your fantastic rom?
Click to expand...
Click to collapse
I don't know, maybe an unknonw (for me) registry trick, I analyzed more that one time the registry entries, and all seems to be ok, but cannot show it, for now.
Just start kit. For further cooking.
Based at official release (and stable, I hope,- don't like to be beta-tester for HTC "in the dark").
It's new way for me (just began to use WinMob by Diamond), so don't bite me too much
Don't forget about Hard-SPL!
Few cosmetic changes & a little tweaked. UC ready.
In OEM left TouchFlo only.
In SYS out: OneNote, PowerPoint, WindowsLive, Help & other rubbish.
In "Install" folder - example only. You can change it to your own provider (look to OEM\CONNECTIONSETUPDB - password I found at XDA) or just use ConnectionSetup.
The most tweaks - in OEM\xxxconfig
Be careful to finish.xml - it's important file!
(return to "Internal Storage". Manila start including in this file too. You can customise it up to you. Same as *.rgu in this folder)
To find the bugs&errors better together, I think
Ideas&remarks - welcome!
It's OPEN PROJECT.
Kitchen: http://rapidshare.com/files/143594363/WWE_1.93.479.3_kitchen.zip
Example ROM (with pass for provision.zip):
http://rapidshare.com/files/143600258/1.93.19965.Light.rar
For make the same - just press !COOK.CMD in the kitchen.
Lighted packages:
http://rapidshare.com/files/144298572/PACKAGE_Diamond_PhoneCanvas.RAR
http://rapidshare.com/files/144138802/PACKAGE_Diamond_QuickGPS.RAR
The trick - in change heavy bmp files to compressed/indexed png.
And patched dll/exe, for use another files.
Not sure about using system resources in this way - up to you. Try.
Changes: http://rapidshare.com/files/144298443/changes_to_kitchen.rar
(Corrected ROM container: 19965 now. Was 20273 - just mistake. And help engine)
can I just install your rom on my Diamond?
Would like to try it, but dont want to fool around with the Kichen stuff
Been reading much on cooking the last days. This looks like a good start!
Thanks for sharing. Hope I can create my own Diamond ROM from here. If it's good enough for some of my friends I will share it on XDA as well
teddyen66 said:
can I just install your rom on my Diamond?
Click to expand...
Click to collapse
Not see the reason - only base functions.
You are right, but it's the fastest ROM I've ever tried
But like you said, it's very basic. Camera is not working, so you need to add all these yourself.
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
It does seem to extract just normal. Is the RAR file save?
update: You might even remove the Office part from the light ROM??
mccune said:
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
Click to expand...
Click to collapse
Hm. "Top" level - zip. Inside - rar. Going to try download back. May be corrupted...
No, everything OK to archive.
I use rar v.3.71
mccune said:
You might even remove the Office part from the light ROM??
Click to expand...
Click to collapse
Word & Excel till alive
mccune said:
You are right, but it's the fastest ROM I've ever tried
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
It does seem to extract just normal. Is the RAR file save?
Click to expand...
Click to collapse
Its 7-Zip i think extracts ok
I will give this a try, other kitchens didn't work out for me very well.
Thanks man ...
Help system
I think idea to remove the help system absolutely is not the best.
Sometimes apps need it for normal work. May keep help engine alive?
Any opinions?
Please tell me one usefull hint that's provided to you because of the Help function?
For me it's wasted space on every device I've owned. If I encounter any problem they go beyond the help files
Looks pretty complicated with no real guide, will look into other kitchens!
I talk about engine (hwhelp) only. The most help files - "dead cargo", of course.
After try to push "help" button at some apps - error, could make system unstable.
P.S. made two "light" packages. ( see in the first post).
It use a little less memory, I hope.
Congratulations for this new project! If you need any help about a multilanguage (Italian) version... I'm ready!
sev7en said:
Congratulations for this new project! If you need any help about a multilanguage (Italian) version... I'm ready!
Click to expand...
Click to collapse
Thanks for support
I think, change the locale - it's only change the *.mui & may be other files in folders *_0409. Change to Italian locale - _0***, don't know exactly.
Could you try it?
Found the mistake - "alien" rom container (from 20273) in the kitchen.
Just accident.
May be it's nothing, but...
- in the first post + hwhelp.exe: changes_to_kitchen.rar
Tricks
Stop unused services (functional don't loose) - will start on demand:
[HKEY_LOCAL_MACHINE\Services\BTAGSVC]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\BthAsPlugin]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\BTHIDSVC]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\OBEX]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\QuickGPS]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\WirelessService]
"Flags"=dword:00000004
It's THE SAMPLE. (but I use it)
May stop any more? Biotouch, for example?
------------------------------------------------------------------------
Start HTCVolumeControl.dll without taskmanager, or if you use another TM:
[-HKEY_CURRENT_USER\Software\HTC\BootLauncher\Services\HTCVOLUME]
[HKEY_LOCAL_MACHINE\Services\HTCVOLUME]
"Dll"="HTCVolumeControl.dll"
"Order"=dword:0000000c
"Index"=dword:00000000
"Info"=dword:00000000
"Prefix"="VOL"
Tested on Raphael VolumeControl
------------------------------------------------------------------------
Somebody can explain how to (EXACTLY! step by step) change OS, XIP, SYS in this kitchen? I've read a lot of tutorial but I didn't understand how...
In example, I've got:
1) this kitchen and this "base" rom
2) another diamond rom with 20748 xip build.
If I would to update OS, XIP and SYS to newer, what I have to do?!
GriFolle said:
Somebody can explain how to (EXACTLY! step by step) change OS, XIP, SYS in this kitchen? I've read a lot of tutorial but I didn't understand how...
In example, I've got:
1) this kitchen and this "base" rom
Click to expand...
Click to collapse
You don't neet "base" rom (or what you mean?) it's example only.
If you talk about rom\os.nb in the kitchen - it's just container for rom, which is empty.
GriFolle said:
2) another diamond rom with 20748 xip build.
If I would to update OS, XIP and SYS to newer, what I have to do?!
Click to expand...
Click to collapse
Just delete oem, rom, sys & make you own "tree"
Thanks for your very QUICK reply Modilv!
So, I have just to take the parts of (maybe more) diamond romS that I need (including OS.nb??) and put theme in your kitchen..?
So simple?!
PS: no "porting" xip or something like that?
TIA
It't not "my" kitchen (just add bepe's utility to final step)
I made the "tree" only.
You can do the same.
So, I set up my own kitchen based on the EasyPortOven and Bepes last WM6.1 Kitchen, added newer BuildOS and use it now with the Build 21215 SYS of xperia x1 with QVGA files and XIP of a Kaiser.
My problem is, that everything runs fine, until it comes to the point where it starts buildxip.
I just don't understand it.
Maybe somebody could have a look on it?
Here is the link:
http://www.4shared.com/file/103415760/304c8459/Kitchen.html
ice8lue said:
When I'm trying to cook my ROM using BuildOS, everything works fine, but the it shows an error, last status "Creating shadow order file..."
How can I fix this?
I updated BuildOS to v4.2b3 and it works but, after G'Reloc-ing I also get an Error about RadioButton1... ???
Click to expand...
Click to collapse
Solution for Error about RadioButton1...
Make sure you have a Create_ROM_for_Hermes.bat inside your 'Tools' Folder...
User Search menu (upper right) and look for Ervius Kitchen batch files... or
use ivan's or josh's kitchen tools...
OK, this is working now. Now Portxip.exe is crashing -.-
Tools Folder
Remove your tools folder and replace it with this one...
link
and Add this folder to your kitchen to... this folder is where the image of your New ROM will be created...link2
G'Reloc says I/O error 105 -.-
oh man this is annoying xD
thx for your help bro =)
I just don't get it, buildxip is crashing all the time...
I'll upload my kitchen here, maybe you could have a look on it?
try to replace your xip... or your OS.nb.payload
i've downloaded your kitchen and seems that there are too many problems ...
Try reading this first... especially the part wherein you need to study RAM allocation ...
First thx for helping me
I was trying to port a XIP from Touch Cruise
Yet it cant even boot in the system [only suck at the screen with the red words at the bottom]
Any clear tutorial for me. Thank you
You cannot just use the XIP from another phone.
You must get the XIP split into OEMXIPKernel and MSXIPKernel so that you can combine the new MSXIP with your existing Trinity OEMXIP.
And most of the time you would need to use the new build's SYS packages that go along with that new MSXIP.
What kitchen are using? Ervius Visual Kitchen?
the.decoy said:
You cannot just use the XIP from another phone.
You must get the XIP split into OEMXIPKernel and MSXIPKernel so that you can combine the new MSXIP with your existing Trinity OEMXIP.
And most of the time you would need to use the new build's SYS packages that go along with that new MSXIP.
What kitchen are using? Ervius Visual Kitchen?
Click to expand...
Click to collapse
Yes i am using Ervius Visual Kitchen
What i do is using the xipporterex to port the xip.
I even tried to follow the bepe tutorial from darkforceteam with bepe kitchen.
Yet same error occured.
Would u mind giving me a clear step for making it workable?
thx
Sorry but I have always used pre-extracted XIP/SYS bundles from people like Da_G that I then put into my kitchen. So I am not sure I can give you a full step through for porting the TC xip/sys from scratch.
One thing about the OEMXIP though, whenever I have used xipporterex I usually discard the generated ROM\Trinity\NEWBUILD# and replace it with a copy of my existing ROM\Trinity\OLDBUILD# (I just rename the folder to the new build number). It is just the ported ROM\Shared\NEWBUILD# folder that you want.
Again, you are also using the SYS\NEWBUILD# folder aren't you?
the.decoy said:
Sorry but I have always used pre-extracted XIP/SYS bundles from people like Da_G that I then put into my kitchen. So I am not sure I can give you a full step through for porting the TC xip/sys from scratch.
One thing about the OEMXIP though, whenever I have used xipporterex I usually discard the generated ROM\Trinity\NEWBUILD# and replace it with a copy of my existing ROM\Trinity\OLDBUILD# (I just rename the folder to the new build number). It is just the ported ROM\Shared\NEWBUILD# folder that you want.
Again, you are also using the SYS\NEWBUILD# folder aren't you?
Click to expand...
Click to collapse
Oh man! You are genius!!!
My rom comes bootable after renaming the folder!
That's so fantastic
Yet the xip of the system seems hasn't update [still the old build ]
Update
I used the old Build.. therefore, my device is bootable....
Yet when i choose back the new build, ext xip and sys as the neew version,
it suck again at the screen...
Thx man i know u have tried a lot to figure out my problem.
Is it possible or better, if i upload my kitchen for u to check?
OPzero said:
Oh man! You are genius!!!
My rom comes bootable after renaming the folder!
That's so fantastic
Yet the xip of the system seems hasn't update [still the old build ]
Click to expand...
Click to collapse
Oh thats easy. The "Rom Version" (that shows on boot) just needs to be patched (it is reading it from the copied OEMXIP).
Just go back into the Porting window then click the button "Find Date/Version on \ROM\Xip\"
That will populate the Rom Date and Rom Version fields.
You can then edit those fields and click each of the "Change" buttons to patch the newer Date/Version into the OEMXIP
You can also set the PagePool value using the "Change PP to Mb" function (it is not possible to query the current PP value however it does tell you what it previously was when you change it). You could always set it to something sensible like 4 or 6 and see what it was before that.
EDIT: If you were actually talking about the CE OS build number that shows in "About Device" then that is much harder to change. It is embedded somewhere within the MSXIP (requires hex editing I am not familiar with - and that is effectively make a "fake" build anyway).
OPzero said:
Update
I used the old Build.. therefore, my device is bootable....
Yet when i choose back the new build, ext xip and sys as the neew version,
it suck again at the screen...
Thx man i know u have tried a lot to figure out my problem.
Is it possible or better, if i upload my kitchen for u to check?
Click to expand...
Click to collapse
Oh, sorry just saw this ... yeah probably better to just do that.
Just curious but why on earth do you want to port some old TC 6.1 rom anyway?
There a plenty of functional WM6.5 xip/sys bundles that we can/have ported to Trinity. Even if it has be WM6.1 there are surely newer releases of 6.1 xip/sys to choose from?
EDIT: Just a heads up but I am about to go offline for the night (end of the work day in my timezone) so if you do upload I will not reply until tomorrow.
the.decoy said:
Oh, sorry just saw this ... yeah probably better to just do that.
Just curious but why on earth do you want to port some old TC 6.1 rom anyway?
There a plenty of functional WM6.5 xip/sys bundles that we can/have ported to Trinity. Even if it has be WM6.1 there are surely newer releases of 6.1 xip/sys to choose from?
EDIT: Just a heads up but I am about to go offline for the night (end of the work day in my timezone) so if you do upload I will not reply until tomorrow.
Click to expand...
Click to collapse
It's ok, would u mind pm or post some link which release those stuff?
Thank you very much!
I will still upload my rom and pm to u~
Check it when u hav time
really really thx
You could extract the 23102 wm6.5 build from my last kitchen release:
http://forum.xda-developers.com/showthread.php?p=5547181#post5547181
I have modified EVK slightly to allow it to build either p3600i or Trinity ROMs from the same kitchen but still there is a full QVGA xip/sys bundle there for 23102 (give or take a few sys packages).
Got to go, will try and be more helpful tomorrow
the.decoy said:
You could extract the 23102 wm6.5 build from my last kitchen release:
http://forum.xda-developers.com/showthread.php?p=5547181#post5547181
I have modified EVK slightly to allow it to build either p3600i or Trinity ROMs from the same kitchen but still there is a full QVGA xip/sys bundle there for 23102 (give or take a few sys packages).
Got to go, will try and be more helpful tomorrow
Click to expand...
Click to collapse
Yes I got it~ Thx
it is great
OK and now i am going to mod it~~
Yet just before i start, would u like suggesting me some post that is most updated and clear enough for me such a newbie to work around it?
Thx
OPzero said:
Yes I got it~ Thx
it is great
OK and now i am going to mod it~~
Yet just before i start, would u like suggesting me some post that is most updated and clear enough for me such a newbie to work around it?
Thx
Click to expand...
Click to collapse
Go and find SuperSport's Tutorial Video for using Ervius Kitchen.
I have broken up the EXT packages into categories to make it simpler for new chefs but the basic concept is the same.
I have included pre-built ROM profiles to make it very simple to build ROMs out-of-the-box.
Just got to "Load ROM", choose one for your phone (P3600i or Trinity) and the click "Create ROM" to build it.
Load a few different profiles and look at what changes in the settings. That should help you see what is going on.
Check out this thread for more tutorials and guides:
http://forum.xda-developers.com/showthread.php?t=669414
the.decoy said:
Go and find SuperSport's Tutorial Video for using Ervius Kitchen.
I have broken up the EXT packages into categories to make it simpler for new chefs but the basic concept is the same.
I have included pre-built ROM profiles to make it very simple to build ROMs out-of-the-box.
Just got to "Load ROM", choose one for your phone (P3600i or Trinity) and the click "Create ROM" to build it.
Load a few different profiles and look at what changes in the settings. That should help you see what is going on.
Check out this thread for more tutorials and guides:
http://forum.xda-developers.com/showthread.php?t=669414
Click to expand...
Click to collapse
1 more question
I downloaded a XIP SYS Pack from
http://forum.xda-developers.com/showthread.php?t=650783
However there are 5 Folders
How can i port them into the kitchen?
Thx for that
OK, this technically requires more time than I can spare to explain thoroughly ... but maybe if I just outline the steps you can do some google searching to work out exactly how to do it:
- First you need to clean up the SYS for you needs. For Trinity you need to have QVGA sys structure so that means only 96DPI and 320x240
- That means sorting the SYS package folders into an EVK SYS structure and removing the other DPI and resolution folder structures.
- Go get XIPDumpSoter (or whatever it is called now) by teh penguin so that you can use it to automatically sort the folders. Then delete any that are for other DPI or RES (eg: 192DPI or 640x480, etc). You _only_ want 96DPI and 320x240 (and of course any that are non-res specific)
- That should give you the folder structure to put into \SYS\NEWBUILD#\
- You will need to copy over the WINCENLS sys package from your existing SYS as that will not be in the new SYS (there are other replacement folders like SQM_DUMMY, and also some that we often just delete but you can learn that stuff later)
- We have already discussed what you need to do with the MSXIP
- Lastly, (and this is really very much the "art vs sicence" part), you will need to go through and "recmod" a certain number of "modules" within certain sys packages.
I simply don't have the time right now to get into recmod but if you google you will find plenty of helpful posts explaining it. I think there is even a basic recipe of what to recmod for 64M users done by JooJooBee ... that would get you going.
Put simply, at this stage you need to read read read read read lots of chef threads to pick up the finer details. Sorry I am too busy at work to be any more help than this.
Good luck.
Thank you for spending time on me
I know it is rather annoying to explain a few things
Really Really Thank you for helping me
I hope that my post could be a guide for others
Update:
The rom is still unbootable after a day of trying.
Does the OEM section be edit before updating the build?
Such as initflashfiles.dat [I read the in the tutorial that it should change to the native 6.5]
May be i started from the wrong step?
What i concern is that wm6 may not suitable to update directly to wm6.1 or wm6.5
Thank you for spending much time on helping me
If it can be google, simply give me the keyword,
I will finish the entiry
And finally, thank you!!
OPzero said:
Thank you for spending time on me
I know it is rather annoying to explain a few things
Really Really Thank you for helping me
I hope that my post could be a guide for others
Update:
The rom is still unbootable after a day of trying.
Does the OEM section be edit before updating the build?
Such as initflashfiles.dat [I read the in the tutorial that it should change to the native 6.5]
May be i started from the wrong step?
What i concern is that wm6 may not suitable to update directly to wm6.1 or wm6.5
Thank you for spending much time on helping me
If it can be google, simply give me the keyword,
I will finish the entiry
And finally, thank you!!
Click to expand...
Click to collapse
I'm actually going to bed before 3am tonight, so I will not be long here, but I just had a thought. When you cook the ROM, are you checking "Real WM 6.5 AKU" in the Kitchen? Don't do that. You cannot actually use a Native 6.5 Kernel on the Trinity as one does not exist. Also, as mentioned by the.Decoy before, you MUST have 'wince.nls' in your Kitchen somewhere or it will not boot. Thirdly, try cooking a version without ANY Extended packages. Only the original XIP and SYS and see if that boots. When you get that going smoothly, start adding EXT packages. Good Luck!
I'll check back in a couple days to see if you've made any progress. If you'd like to send your kitchen to me also, I'd be happy to look it over and see if I can find anything wrong in there.
Again and Again
I keep remind myself that Native 6.5 Kernel should be checked
OMG The Bug is here
And Thanks Decoy
Thank You
Thank You!!!!!!!!!!!!
================================
Update:
I saw a folder called 0_ROM_Version in EXT Shared
What is it and what function does it have?
Thx
OPzero said:
Does the OEM section be edit before updating the build?
Such as initflashfiles.dat [I read the in the tutorial that it should change to the native 6.5]
Click to expand...
Click to collapse
Ummm are you trying to use a freshly extracted OEM from an official ROM?
If so then yes, there is a massive amount of conversion that must be done to it before you an cook it into a rom. Even before you break it up in to components and edit all the reg and dat files ... you first need re-sign everything with an SDK cert because you won't have the official cert that HTC built them with.
Seriously. If you are just starting out then use an existing chef's OEM (use mine or anyone else who has posted a kitchen).
Even I have not yet ever had the time to complete build an OEM from scratch (not that I don't want to one day). I was always just adapting the OEM that Chanvi had provided us in his kitchen, primarily because he had already done all the work to make it mesh with WM6.5
OPzero said:
Again and Again
I keep remind myself that Native 6.5 Kernel should be checked
OMG The Bug is here
And Thanks Decoy
Thank You
Thank You!!!!!!!!!!!!
================================
Click to expand...
Click to collapse
I am bit confused by what you said there
As Supersport explained, we do not have a Native 6.5 kernel for Trinity.
So that option should not be checked.
OPzero said:
I saw a folder called 0_ROM_Version in EXT Shared
What is it and what function does it have?
Thx
Click to expand...
Click to collapse
Again, this is why I said to try "Load ROM" and see what happened
Those are just simply EXT packages which contain 1 single provxml. Each one sets the registry value for "ROM Version" (the info that comes up in "About Device" in Settings). There is one for every type of "Saved ROM" you can build from that kitchen.
I created them so that people could build each of the several types of rom from my kitchen but never need to edit the provxml files to change what the version info was.
If you are going to try cooking your own roms, the best advice I can give you is find a text editor you like and just start opening up ALL of the REG DAT RGU and PROVXML files you can find and see what they are doing.
You can even do it from within EVK. Select the type of file on the left panel called "Editors" (or just select "All") then click "Show Editor". You can open the files it finds by double clicking them in the panel on the right.
Anything custom that ever happens in the setup of a rom is controlled by these files.
If you want to see how something works (or what it does), just open up the files and read them
Sorry, wt i mean is that my rom become bootable after unchecking it
~~ That is so amazing ~~
Now i am Reading the horrible, endless.....etc tutorial, [I can finally have my own rom ]
1 Question, I am trying to put a new wince.nls which content much more countries in the rom. Yet it comes unbootable after i have repalced it.
I googled around and found several solutions.
1 is that i should put it in OEM rather than SYS [I havn't ried it yet i think it won't work]
2 is that i should mod the size of the xip.bin
Therefore it is big enough to store it.
3 Adding in some registry with my selected country code
Thanks for helping me ~~
Sorry can't help you there.
I have never ventured beyond WWE lang for my kitchens.
OPzero said:
1 Question, I am trying to put a new wince.nls which content much more countries in the rom. Yet it comes unbootable after i have repalced it.
I googled around and found several solutions.
1 is that i should put it in OEM rather than SYS [I havn't ried it yet i think it won't work]
2 is that i should mod the size of the xip.bin
Therefore it is big enough to store it.
3 Adding in some registry with my selected country code
Thanks for helping me ~~
Click to expand...
Click to collapse