Develop Bugs

Diamond ROM Cooking questions

Dear All,
After messing around with the tweaks here on the forum, I wanted to build my own ROM.
I want it to be:
-Fast (With the known registry tweaks)
-Stable
-Graphically nice
-With the apps I like
-To have Dutch language, with an extra WWE-XT9
-With the latest OS version (.721)
My plan to do this is:
-Get a good (modded-) BaseROM (I have SkippyCentraal 2.8 in mind)
-Remove all unwanted programs
-Exchange the OS.nb (128Mb, .273) with the extracted OS.nb (.721) from a different (non-Dutch) firmware
-Cook it together and flash it to my Diamond
-Make registry changes
-Dump my own (cooked and tweaker .721-) ROM
-Compile again
-Post it here ;-)
Is this just the way it works? I have just read Lolek47's Tutorial Thread
http://forum.xda-developers.com/showthread.php?t=413782
and it seems that simple?
Please advice...
Thanks in advance!
BR Bart
The Netherlands

When I saw the tutorial I thought it is simple. But when really doing it, it is not that simple: my cooked ROM's (so far all of them) aren't even starting up. Hangups all over the place.
My advice to you is: find a good kitchen and just do it. Eventually you wil cook a decent working ROM. But don't expect to do it in a few days (like I did)

BUMP!
ive got the same plan as burdie!
But just in the WWE language, somebody knows a good tutorial?
would really like it!
yourz,
ruubs

I can offer some advice, coming from cooking on a Kaiser:
I think everyone would like to make a ROM with all those things listed While it may not be impossible, it may take quite some time tweaking it just the way you want it
1. You can't use any ROM as a base ROM unless it is chef-friendly. This means that all the .dsm and .rgu files are included. If they aren't, I'd recommend starting from scratch on the latest or most stable base ROM
2. Removing programs should be easy, because all the Diamond's are organized in .dsm files instead of all being dropped in the OEMAPPS folder like the Kaiser
3. I don't really see the point of having a WWE XT9 dictionary with a dutch ROM, care to explain. Also, what are you trying to do with replacing the OS.nb?
4. I'd not recommend dumping the ROM off your diamond then compiling it. Why would you go through all that trouble when you could just make the registry tweaks you want and then cook it up?
i'd be glad to elaborate on any more of these or answer any other questions you have

ruubs said:
BUMP!
ive got the same plan as burdie!
But just in the WWE language, somebody knows a good tutorial?
would really like it!
yourz,
ruubs
Click to expand...
Click to collapse
hi,
short but very usefull rules from
http://forum.xda-developers.com/showthread.php?t=508293
nothing is better than (electronic) paper ...

Japanese WM6.1 ROM for X01HT

being tired of seeing too many protected roms floating around, i decided to make japanese wm6.1 cooking base files myself. it took me awhile, but i finally figured it out. i would like to share my experience of making a japanese wm6.1 rom for hermes here.
actually, it is not that difficult, and all i did was just assembling pieces from different official roms. so, i would NEVER call it my OWN rom or anything because every part of the original roms was developed by MS and HTC. (sorry, but i really think it's too funny many people, who know slightly better than others, put their names in the ver info, apply procection or whatever to their roms, and say "this is my own rom!" for something made out of other roms originally built by MS and HTC.... is this place for dev info sharing for similar-minded guys? donations?? c'mon!)
i will explain about the details step by step later. here's a rough tutorial.
things you need:
[tools]
Pandora Kitchen (thanks to mattk_r) for cooking and burning
http://forum.xda-developers.com/showpost.php?p=1364931&postcount=1
or
i prefer bepe's Extended Hermes Kitchen for WM6.1
http://rapidshare.com/files/88850555/HERMES_DEV_v2.1_Build_19199.rar
G'Reloc.exe as usual
http://forum.xda-developers.com/showpost.php?p=1524413&postcount=1
[roms]
bepe's kitchen (thanks to him!) for simple and working oem folder and xip (OEMXIPKernel only)
http://forum.xda-developers.com/showpost.php?p=1177762&postcount=1
x04ht (japanese softbank diamond) rom for most of the sys part
http://forum.xda-developers.com/showpost.php?p=2998164&postcount=1
htc hermes official wm6.0 rom simply for os.nb as a template
http://rapidshare.com/files/46467733/HTC_TyTN_WWE_3.54.255.3_6275_1.48.00.10_108.exe
htc kaiser (or opal) official wm6.1 rom for dpi_96 files
http://rapidshare.com/files/157469239/Kaiser_HTC_ASIA_HK_WWE_3.34.721.2.rar
http://forum.xda-developers.com/showthread.php?t=441689
s11ht (japanese emobile kaiser) official rom for 0411_dpi_96
ftp://htc-jp.com/EM/S11HT_firm_V2_6_881_0_JPN.exe
[basic strategy]
[oem]
1) bepe's oem folder is very simple and clean for cooking (some modifications are necessary in *.rgu files, tho)
2) replace OEM.cer by the one from x04ht rom
[rom]
1) basically, you can take OEMXIPKernel from bepe's xip or from htc hermes official wm6.0 rom
2) MSXIPKernel and MSXIPKernelLTK are from x04ht rom or whatever you want
3) use os.nb from htc hermes official wm6.0 rom just as a template
[sys] (tricky)
1) the base is opal sys. but remove all the language specific (0409) folders.
2) take the language specific but non-vga folders from x04ht, x05ht or whatever wm6.1 japanese rom (0411 folders not including dpi_192)
3) take language specific qvga folders (the 0411_DPI_96 folders) from s11ht
4) take .vm folder, packages.* in metadata folder, and service.exe in os folder, shell32.exe and shellres.dll in shell folder from hermes official or bepe's sys. (irda is not included in opal rom. take them from bepe's rom if you wanna use irda.)
[points]
1) don't forget to copy WinCENLS_Lang_0411 into your sys. otherwise, the device does not boot since WinCENLS_Lang_0411 is not included in xip.
2) if you take sys from any newer versions, taskmgr does not work since it is not signed by softbank. remove mxipupdate_taskmgr_shell_1.provxml in base_lang_0411. it's useless, anyway.
3) this method does not create shotcuts in windows\appbuttons. you need create those shortcuts with japanese names yourself to make the buttons work properly. (does anyone know how these shortcuts are automatically created?)
4) os ver info is stored in the original files. (read here for details: http://forum.xda-developers.com/showpost.php?p=1172925&postcount=1) you can change the ver info as you want, but i REALLY hate to see ver info with someone's name or some personally customized splash screeens. so, the ver info does not reflect the actual ver you take all the files from.
5) i don't think this works only with hermes but with any other qvga devices (you have to change xip part.) hope many other qvga device users can make (assemple?) their own japanese wm6.1 roms freely.
question:
i made a shortcut file with 14 japanese (2 byte) letters and put it in the windows directory, but the hermes did not boot. i changed the name to 13 japanese letters, and then it booted... are there any filename restrictions for east asian language files??

reserved for step-by-step guide

here is the japanese wm6.1 cooking base files for hermes
sys: 21014
xip: 21014
oem: basically based on htc oem
http://www.mediafire.com/?3almqggzvgy (OS.NB.payload is not included. place one in rom folder.)
sys: 20931
xip: 20931
oem: basically based on bepe's oem
others: commmanager and calc replaced for the touch looks
note: i did not modified the ver info in shellres.dll.0411.mui, and the ver info shown in control panel does not reflect the real os ver.
note2: this file is just for cookers. i will not provide the rom tuned up for my own use. i will not response to "please send me your rom" requests. (sorry)
link
http://www.mediafire.com/?2gfymtframj
you can use these files FREELY since i simply assembled them from the other roms. they don't belong to be from the beginning. (.VM is not included. take it from another hermes rom to cook it!!)
happy new year, and happy cooking!

Congrats and welcome to hermes cooking sir. if you need a copy of a unprotected rom of mine, just let me know, PM or post
Peace sir,
Joshua

Very big thank for you...
qtotter said:
sys: 20931
xip: 20931
oem: basically based on bepe's oem
others: commmanager and calc replaced for the touch looks
note: i did not modified the ver info in shellres.dll.0411.mui, and the ver info shown in control panel does not reflect the real os ver.
note2: this file is just for cookers. i will not provide the rom tuned up for my own use. i will not response to "please send me your rom" requests. (sorry)
link
http://www.mediafire.com/?2gfymtframj
you can use these files FREELY since i simply assembled them from the other roms. they don't belong to be from the beginning.
happy new year, and happy cooking!
Click to expand...
Click to collapse
I'm Andy. Thank you very much, qtotter-san.
Lately I've been thinkin about changing my handheld (I'm using BA and MPx200 at this moment). But, despite my condition as a Japanese language student, I would love to have a Handheld powered by Japanese Windows OS. To buy Japan's handheld seems to expensive for me, so I decided to search for Japanese ROM first, then decide which one shall I buy.
I've been searching all the time for Japanese ROM (not 日本語化 ROM but 日本語版 ROM FILES), n finally, look what I found here, not only Japanese ROM, but Hermes WM6.1 Japanese cooking base (very big thanks ^o^). I've tried to search in xda-developers, and some other forum, but still unable to find Japanese ROM. I'd also sent private messages to Japanese developers here, but still I have no idea where to find Japanese ROM.
And now, I found this thread. This really helps me.
心から感謝を申し上げます。(kokoro kara kansha wo moushiagemasu)
Once again thank You very much, qtotter-san. I really appreciate your hardwork.

qtotter said:
sys: 20931
xip: 20931
oem: basically based on bepe's oem
others: commmanager and calc replaced for the touch looks
note: i did not modified the ver info in shellres.dll.0411.mui, and the ver info shown in control panel does not reflect the real os ver.
note2: this file is just for cookers. i will not provide the rom tuned up for my own use. i will not response to "please send me your rom" requests. (sorry)
link
http://rapidshare.com/files/178421014/hermes_jpn_wm6.1_cooking_base.zip.html
you can use these files FREELY since i simply assembled them from the other roms. they don't belong to be from the beginning.
happy new year, and happy cooking!
Click to expand...
Click to collapse
can't download not....can you release again? I want to cook JP 6.1 too...thanks a lot!!

could anyone tell me how to build OEM MMSLite?

antony34 said:
can't download not....can you release again? I want to cook JP 6.1 too...thanks a lot!!
Click to expand...
Click to collapse
it seems like it's been downloaded 10 times, already... the link has been updated.
qt

qtotter said:
it seems like it's been downloaded 10 times, already... the link has been updated.
qt
Click to expand...
Click to collapse
Thanks a lot!!!

I hope the explanation of WM6.5,please!

Opal/Diamond Dialpad
if you use opal dialpad with japanese wm6.1 rom, smart dialing stops working. i happened to find a solution while playing with my diamond. just delete the following reg key to make smart dialing work.
[HKEY_LOCAL_MACHINE\Security\Phone\PhoneKeyMatch]
"SmartFilterFlags"=dword:00000002
This entry is in the *.rgu of Base_Lang_0411.

Download won't start
Is anything wrong with the server?

Woops!
Problem solved by deleting temporary internet files

updated japanese wm6.1 base to 21014
i will update msg #3 shortly.

Thanks qtotter sann!
but BT seem have problem, once flash it. it show have not BT device...

antony34 said:
Thanks qtotter sann!
but BT seem have problem, once flash it. it show have not BT device...
Click to expand...
Click to collapse
no bt applications are included. (drivers are included.) please use any bt apps from your favorite roms.

qtotter said:
no bt applications are included. (drivers are included.) please use any bt apps from your favorite roms.
Click to expand...
Click to collapse
But I can't avaliable BT at comm manager...

antony34 said:
But I can't avaliable BT at comm manager...
Click to expand...
Click to collapse
confirmed. i will check what causes this later.

May I ask some one to upload a COOKED Japanese rom?
I am far from to play with Hermes, have switched to Raphael.

qtotter said:
confirmed. i will check what causes this later.
Click to expand...
Click to collapse
qtotter sann,
Wifi & Camera seem also have problem.
Wifi & Camera sometime got error when avaliable.
I will keep report if still have problem or bug.
Thanks!

[KITCHEN+ROM][WWE]Stock Diamond 2.03 Kitchen & Rom ported with 21042XIP/SYS (Online)

[KITCHEN+ROM][WWE]Stock Diamond 2.03 Kitchen & Rom ported with 21042XIP/SYS (Online)
I've seen a few requests for kitchen's & rom's based on 21042 XIP/SYS so I decided to knock one up using the 2.03MRII 2.03.401.3 base and XIP/SYS from 21042 build.
This kitchen & rom is currently completely stock. Nothing removed from the OEM & SYS folders, no tweaks no addon programs just standard diamond build with newer core.
The only extra included which isn't in the original stock rom is remote desktop mobile (came with the sys not an extra) which of course you can remove from the kitchen if you wish. As it's the new sys it obviously contains the newer builds of MS apps including Windows live. Also this does not have the newer version of IE, just standard version.
Keyboard currently supports English, French, German, Greek, Italian & Spanish t9 however this should be updatable with the 14 language patch available elsewhere.
The kitchen is bepe platformrebuilder in almost stock form. No extra tools except for it runs htc rom tool to build the nbh file at the end.
XIP is not changed in anyway except updated msxipkernel & msxipkernelltk from 21042. No pagepool patching, cert patching or time/date/name changes. os.nb.payload size is reduced in the kitchen however this has no bearing on the final rom.
As this uses bepe's platformrebuilder, if you wish to change the date, build, pagepool, cert patching in the kitchen directly, these need to be done on nk.exe in the oemxipkernel. Any changes made to os.nb.payload (except uldr) will not be carried forward to the final rom as the nk.exe will overwrite changes to the payload. The payload itself is not ported so if you extract this and replace the msxipkernel folders then you will be back to a 20764 xip. There is no need to port the payload as replacing the msxipkernel & ltk folder in the xip folder properly ports the xip anyway if you are using bepe's kitchen (surface kitchen does not work properly in this way)
Also any rom's built with this tool are automatically locked as the kitchen deletes rgu's & dsm's from the cooked rom for space saving and performance. The files are extractable but then all you get is a dump of the files, without being able to seperate to packages.
Hope this helps some of you out there.
Also on the link there will be a stock diamond rom built from this kitchen - entirely stock but with latest xip/sys - even .netcf is still v2.0 that's how stock it is. It does however have more storage memory as it is cooked - original has 82Mb total and 57 available - this has 102Mb in total and 75+Mb free. Using the kitchen you could make a rom with alot more free space however.
I would recommend atleast upgrading .netcf to 3.5 in this rom if you are lightly cooking. Package for this is available on the forum
If you release a rom using this kitchen, please do not forget to credit the source.
Shaks.P Roms are free and always will be. If you like my Roms optionally send me a drink here:
​

Download Links:
http://diamond.geg0r.de/index.php?dir=Shaks%2FStock%2F
Please donate to bl0w for providing this mirror.
Important: Hard spl is required to use either the rom on this link or any rom created with this kitchen.

Basic Tutorial
As the rom is already ported & extracted, all you need to do is make your modifications then build the rom.
Step 1. Modify the sys & oem folders with the packages that you need. Make a backup of any folders you delete in case they cause issues with anything else.
Step 2. Once you are happy with the modifications, run build_rom.bat. This will create the os_new.nb file in the root of the kitchen folder. Once this is done, it will load the htc rom tool that builds & signs the final nbh file.
Step 3. Once the htc rom tool loads, select Build!, Change the version to anyversion you would like (this version only shows up when flashing). Under system, click on ... and select the os_new.nb file that has just been created. Then click on Build! ROM and this will ask where to save the nbh file and the name. Save as diamimg.nbh if you want to flash thru internal storage or any other name you like if using customruu.
Step 4. Ensure your device has hardspl, then flash the rom you just built either using custom ruu or using the internal storage method. If it doesn't work, you can allways flash another rom after getting the device in bootloader mode.

Can't wait
Thanks!

Will you post it today, or....?
And can i make my rom from this "Rom ported with 21042XIP/SYS"?
Thanks!

alxalx said:
Will you post it today, or....?
And can i make my rom from this "Rom ported with 21042XIP/SYS"?
Thanks!
Click to expand...
Click to collapse
It's uploading at the moment. It is a seperate kitchen & a rom as well. You can make whatever type of rom you wish to with this. Just mention the original source if you release it.
The rom is if you want a stock rom with the new build. Looks like you need the kitchen. Should all be uploaded in next 15-20 mins. Had to start the upload again.

Thanks shaks!
Not only do you provide the best ROM around, but now also a kitchen, you rock!

sweat shaks thanx for sharing going to finaly try my own Rom you make us happier and happier every time
(EDIT)
so does this mean your not going to build any more Roms or ?

shaks1979 said:
It's uploading at the moment. It is a seperate kitchen & a rom as well. You can make whatever type of rom you wish to with this. Just mention the original source if you release it.
The rom is if you want a stock rom with the new build. Looks like you need the kitchen. Should all be uploaded in next 15-20 mins. Had to start the upload again.
Click to expand...
Click to collapse
Thanks man! I appreciate it!

Dynomite232 said:
sweat shaks thanx for sharing going to finaly try my own Rom you make us happier and happier every time
(EDIT)
so does this mean your not going to build any more Roms or ?
Click to expand...
Click to collapse
This is just something I felt like doing for today. The kitchen won't get updated much (probably not at all as it's not modified). The roms will continue but will be going for the long release cycles again just like 3.20. I envisage I will probably have one more release and if that doesn't have issues then no more flashing till something big happens again (maybe stable tachi rom comes)
This kitchen is so stock that it can't replace my rom without alot of work - no tweaks, extra packages or anything for that matter except what comes in the stock as that's what some people wanted and I thought it won't take long so I did it.
P.S sorry for the delay with the upload. Having some issues

damn nice to here for one more rom coming out in the near future but tell u the truth my wife went back to rom 3.20 of urs she says it was much beter for her she was used to it she will never change roms agains she says beter for me lol , but mine is doing realy fine and i gots bunch of programs installed no issues at all by the way thanks man i cant stop thanking u

Dynomite232 said:
damn nice to here for one more rom coming out in the near future but tell u the truth my wife went back to rom 3.20 of urs she says it was much beter for her she was used to it she will never change roms agains she says beter for me lol , but mine is doing realy fine and i gots bunch of programs installed no issues at all by the way thanks man i cant stop thanking u
Click to expand...
Click to collapse
Well 3.20 was a damn good, stable, time tested rom. I know a few people who won't change from it at all. Tested the latest but went back to it because they preferred it. 4.x series are a little bit more experimental but still go for the same stability. Next release should take of that small percentage who have corrupt memory/hard reset issues hopefully but I don't expect a big changelog as 4.10 is otherwise fine.

Should the bluetooth work well with this rom?
Thanks!

alxalx said:
Should the bluetooth work well with this rom?
Thanks!
Click to expand...
Click to collapse
Shouldn't be an issue - I use the same sys/xip in my rom without any issues with bluetooth.
Kitchen now online
Rom uploading now. I found if I tried to upload both at the same time, it kept stopping part way!

shaks1979 said:
Shouldn't be an issue - I use the same sys/xip in my rom without any issues with bluetooth.
Kitchen now online
Rom uploading now. I found if I tried to upload both at the same time, it kept stopping part way!
Click to expand...
Click to collapse
Thanks man, downloading now!

hi shaks when u say Modify the sys & oem folders meaning i can delete what i dont want and so on

Dynomite232 said:
hi shaks when u say Modify the sys & oem folders meaning i can delete what i dont want and so on
Click to expand...
Click to collapse
That's right - delete what you don't want, modify rgu's for packages, add your own packages e.g. using ervius package creator to turn a cab into a package or use a package already provided. You'll get lets of cooking help from here (talks about surface kitchen but basic concept the same):
http://forum.xda-developers.com/showthread.php?t=413782
Add your own packages into the OEM folder.

Downloading... In the meantime thank you!

got a question which file is it ? and can i get rid of the keyboard languages and add only the english and swedish ? if anyone
can answer plz and thank you which file is it

Dynomite232 said:
got a question which file is it ? and can i get rid of the keyboard languages and add only the english and swedish ? if anyone
can answer plz and thank you which file is it
Click to expand...
Click to collapse
Add this package to your oem folder for 14 languages & edit the line in the rgu to specify languages you want

[Release] [Kitchen] - SuperJustKitchen v0.9 - Engage!

SuperJustKitchen v0.9 Released.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices, eventually.
Word of warning:
Not all EXT's have been tested or modified for the every device. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.) Some packages will only be compatible with some devices.
(I'm no longer updating each thread separately for each device but just updating my site and posting the release info here. I will only update each thread to say that a new version is out.)
**Warning**
Before using this kitchen, you MUST read the whole thread. Any questions that have been answered will be ignored. This is your only warning.
**Disclaimer**
I am not responsible for any damage that may be done to your phone with a ROM created in this kitchen.
I am not responsible for any damage done to your computer.
I am not responsible for anything... at all.
Introducing SuperJustKitchen!
​ SuperJustKitchen is based on [http://forum.xda-developers.com/member.php?u=843218"]airxtreme[/URL]'s osKitchen Zero. All credit on for the kitchen backend goes to him.
Features
A completely stripped ROM. (Work in progress for some devices.)
LZX and XPR compression (Also option for No compression.)
Auto clean files that are language specific or DPI specific that your ROM does not need
Auto port missing language MUI files
Automatic rec'loc'ing for devices without native 6.5 nk's
6.1 and 6.5 support
Auto XIP and SYS porting
Auto NBH packing
Tool to convert OEM packages to EXT packages
Auto file conflict fix (don't have to removing older file that conflict (not that there are any. )
Save custom ROM settings (for cooks for multiple ROMs)
Cook multiple languages at the same time with the same ROM settings (Have to add language support yourself. I removed the required MUI's a while back because they made updating the kitchen and adding devices a nightmare.)
MUCH better organization of EXT packages
Active development instead of a program that is no longer being developed
Cleaner and easier to use interface
A built-in and customizable Tutorial section
And more!
Builds included
21056 - WM6.1
23658 - WM6.5 with new redesigned GUI
​
At the moment, this is an ENGLISH (WWE) only kitchen. This might change...
NOTE: In order for me to keep track of whether my time was well spent or wasted, if you use this kitchen to make a ROM, please either include SJK in the name or just mention that it was SJK cooked in your ROM's thread.
NOTE: This kitchen assumes that you know how to flash through SD, recover from a bad flash and are able to backtrack your steps to figure out how you broke your own ROM. If you do not understand these, please learn them first. Do not PM me asking me. I have written numerous walkthroughs on all these except on how to backtrack your steps. For that, just remember what you're doing as you do it and keep backups.
If you find any issues, PLEASE report them to the bug tracker in my website. It will help me make this kitchen better!
ENJOY!!!​

Well ... I have repaired my Hermes yesterday and now I'm trying ROMs here and none of them really suits me.
So your SJK came in the right time. I did few ROMs for myself last year, so I'm gonna try your SJK probably this evening.
And if it will work flawlessy, I'm considering donation.

Impressive..
Downloading and will hopefully be trying this out soon.

Let me know if you run into any problems with the native nk and changing the pagepool. (I don't have a test device, unfortunately.)

ivanmmj said:
Let me know if you run into any problems with the native nk and changing the pagepool. (I don't have a test device, unfortunately.)
Click to expand...
Click to collapse
I am cooking a 23529 native build now and will know here soon

Well, I have built 6.5.x ROM with native kernel and 16MB pagepool. I didn't add anything in the ROM and I'm missing Camera, CommManager, ClearStorage and stuff like this in the ROM. Suppose I have to add them externally.
Now I'm gonna try adding some things and changing pagepool etc.

pajousek said:
Well, I have built 6.5.x ROM with native kernel and 16MB pagepool. I didn't add anything in the ROM and I'm missing Camera, CommManager, ClearStorage and stuff like this in the ROM. Suppose I have to add them externally.
Now I'm gonna try adding some things and changing pagepool etc.
Click to expand...
Click to collapse
You have to actually add them in the EXT packages. They are not built in so that you can choose your own. I stripped the OEM and created packages of all required programs and made them into EXT packages.

Ooops, my bad. I've just extracted EXT, SYS, SJK, HERMES archives and didn't check the wrong paths. Because everything puts itself in Sources and the EXT has got Working_Folder/EXT instead of Sources/EXT.
I was wondering why I can't see any EXT things in the osKichten.exe

I must be doing something wrong then cause mine won't go past the boot screen using native. I used everything default. Will try again.

This has happened to me the first time i tried this Kitchen ... then I've tried it again and it worked.
But I'm havning problem with the EXT. I can't select packages from the folders. I can just select folders. :\
EDIT: Ok, I surreder - where are the C_cingular, C_xyz.cab things? I can't find them anywhere to get rid of them.

pajousek said:
Ooops, my bad. I've just extracted EXT, SYS, SJK, HERMES archives and didn't check the wrong paths. Because everything puts itself in Sources and the EXT has got Working_Folder/EXT instead of Sources/EXT.
I was wondering why I can't see any EXT things in the osKichten.exe
Click to expand...
Click to collapse
You have have accidently downloaded v0.7 of the EXT which is a COMPLETELY different kitchen.
This has happened to me the first time i tried this Kitchen ... then I've tried it again and it worked.
But I'm havning problem with the EXT. I can't select packages from the folders. I can just select folders. :\
EDIT: Ok, I surreder - where are the C_cingular, C_xyz.cab things? I can't find them anywhere to get rid of them.
Click to expand...
Click to collapse
I'm not sure what you mean. Can you please post a screenshot?

ivanmmj said:
You have have accidently downloaded v0.7 of the EXT which is a COMPLETELY different kitchen.
I'm not sure what you mean. Can you please post a screenshot?
Click to expand...
Click to collapse
Well, the first issue (not showing apps) was cause by the 0.7 version instead of 0.8 ... i really should give more attention to what I'm downloading.
The EDIT line, about C_Cingular_GoodEmail*.cab, PT_Cingular_Whitelist* etc. - those are apps which are automatically installed after first boot. I suppose it's cause by the line "EXEC:\Extended_ROM\autorun.exe" in PreConfig.txt in OEMOPERATORS. But - where does that autorun.exe has it's config? and where's Extended_ROM in the Kitchen? Because afaik it isn't the same as EXT?
EDIT: I got an idea - aren't those cabs just remains of the ExtROM from AT&T ROM? Then, howto delete them? By making my ROM BigStorage? :|

pajousek said:
Well, the first issue (not showing apps) was cause by the 0.7 version instead of 0.8 ... i really should give more attention to what I'm downloading.
The EDIT line, about C_Cingular_GoodEmail*.cab, PT_Cingular_Whitelist* etc. - those are apps which are automatically installed after first boot. I suppose it's cause by the line "EXEC:\Extended_ROM\autorun.exe" in PreConfig.txt in OEMOPERATORS. But - where does that autorun.exe has it's config? and where's Extended_ROM in the Kitchen? Because afaik it isn't the same as EXT?
EDIT: I got an idea - aren't those cabs just remains of the ExtROM from AT&T ROM? Then, howto delete them? By making my ROM BigStorage? :|
Click to expand...
Click to collapse
Fixed for next build. ^_^
For now, just remove the preconfig.txt file.
Please report any future bugs to the bug tracker. (There are way too many threads to keep track of all of them.)

I've registered to bugtracker ... and the confirmation email didn't come, so I can't post new bugs. I guess I have to post it as guest?

pajousek said:
I've registered to bugtracker ... and the confirmation email didn't come, so I can't post new bugs. I guess I have to post it as guest?
Click to expand...
Click to collapse
I activated you manually. I'm not sure why it's not sending out the emails. I'll look at the code of the site.

I take it this isn't bigstorage? If not do you plan to have one bigstorage? I'd like to be able to do bigstorage in 6.1 and 6.5 and this looks like my best option..
thanks

Since the bugtracker is broken:
These things are buggy:
any Connection Wizard - I can't get it to work
Dialer - Every dialer is buggy and if I try to cook there else OEM Dialer (found by google), it doesn't work too
ClearStorage - doesn't do hardreset
Then I'd appreciate battery.dll which is by 1% and not 10%.
Making the ROM BigStorage would be a big plus too. And AFAIK I shouldn't have 39MB RAM with 6MB PagePool? 39MB is for 16MB PP, right?
MrDSL, are you experiencing anything of these issues too?

pajousek said:
Since the bugtracker is broken:
These things are buggy:
any Connection Wizard - I can't get it to work
Dialer - Every dialer is buggy and if I try to cook there else OEM Dialer (found by google), it doesn't work too
ClearStorage - doesn't do hardreset
Then I'd appreciate battery.dll which is by 1% and not 10%.
Making the ROM BigStorage would be a big plus too. And AFAIK I shouldn't have 39MB RAM with 6MB PagePool? 39MB is for 16MB PP, right?
MrDSL, are you experiencing anything of these issues too?
Click to expand...
Click to collapse
Strange. I'll have to test the connection wizards on the wing.
The dialers work fine on the wing. Does the dialer named Hermes work? (It's directly from the Hermes.)
ClearStorage - Your device might require an older clearstorage. I'll have to look for one.
That sounds like the native 6.5 nk isn't getting its pagepool changed.
I'll see about that. The Hermes 6.5 nk is notorious for most pagepool tools not working on it.
As far as the bigstorage. Give me a link to it and I will see about including it.

well, i'll try the not-native kernel (what disadvantages it has anyways?)
about bigstorage & clearstorage & dialer - i'll do some searching and testing and send you working links (since you don't have testing device).

ivanmmj said:
Strange. I'll have to test the connection wizards on the wing.
The dialers work fine on the wing. Does the dialer named Hermes work? (It's directly from the Hermes.)
ClearStorage - Your device might require an older clearstorage. I'll have to look for one.
That sounds like the native 6.5 nk isn't getting its pagepool changed.
I'll see about that. The Hermes 6.5 nk is notorious for most pagepool tools not working on it.
As far as the bigstorage. Give me a link to it and I will see about including it.
Click to expand...
Click to collapse
I have yet to get a ROM past the boot screen So I dunno..

Help For updating wm6 XIP to wm6.1

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