Develop Bugs

Flashing a Kaiser Rom on to a Hermes

To the Rom chefs out there (btw you guys are the greatest), how difficult would it be to flash a kaiser rom on to a hermes? Would it be impossible or feasible? The reason I ask is that I am intrested in the software features of the kaiser but it will not be available in the states for a while (and my company may not upgrade for a while). I'm not sure how similar devices handle roms but if I could get a hermes with touchflo, built in improved home and com managers, and an app to recognize business cards... well that would rock. Just an idea I would appreciate any feedback.

Itz not difficult... only question is... does it work???

I would love to see that, but that is a hell of a question "Will it work?"!

Here is a short answer for you... HELL NO but if you like try it and then send me your bricked hermes!

Won't work out of the box, but you can extract whatever you want and cook it into your own ROM, using one of existing Hermes ROMs as a base.

Would it be possible to switch out the touch.dll file with the one from the kaiser to try to get touchflo working on the hermes (I'm comfertable setting up the business card recognizer through a cab)?

ok we need members that have created there own cooked roms to give us reallistic insight on how to pull this of?

Cooking a rom
leoiden said:
ok we need members that have created there own cooked roms to give us reallistic insight on how to pull this of?
Click to expand...
Click to collapse
i take no credit for this, i am a noob loke you all, i myself like the att base that i get from vp3G you exrtact the base using romdonalds, you can cook with it to, but i cant understand it, i need to take more time. however i take the base and use it with pandora's build os, i also put added stuff in the pandora with Bennec83's instructions.
any spelling mistakes you find, suck it. i have been up since 4am and i need to get up at 4 again
ROMDonalds Kitchen v1.0 - The Educational Kitchen
http://forum.xda-developers.com/showthread.php?t=319970&highlight=romdonalds
vp3G's WM6 v3.0 -- [The official "official" AT&T ROM]
http://forum.xda-developers.com/showthread.php?t=317952&highlight=vp3G
Pandora Kitchen - v6.0 Build it YOUR way [updated 08/13/07 @ 14:19]http://forum.xda-developers.com/showthread.php?t=316881&highlight=pandora
Bennec83's cab-oem
1: Download CAB Manager from Rapidshare or Megaupload
2: Unpack the CABManager.exe and run it
3: Drop your CAB into CAB manager
4: Extract all the files in the CAB, to do this click the icon 3left from the XML button (It has SEL in small letters at the top of the button) LEAVE THE CABManager.exe RUNNING AS YOU WILL NEED IT FOR STEP 10
5: Go into the folder that you extracted your CAB to, there will be an *.inf (* = Name of the CAB), delete it as it is not needed
6: There will also be another folder inside the directory where you extracted the CAB, this will probably be called "Windows" or "Program Files"
These files contain all the files that are supposed to be in each directory on your device. i.e. all files in "Program Files" will get installed to the "Program Files" on your device when you install the CAB.
Never-the-less, these directories are not needed as we want all the files in the same folder, so copy the contents of each folder, into the folder where you extracted the CAB, do this for all folders that were extracted from the CAB
7: Go Here To Generate A GUID. Set it to "Version 4:Random" and press "Get" (It should look something like this - 21f768ec-4901-11dc-8314-0800200c9a66 - I will Note it as <GUID> instead of loads of numbers for ease of typing)
8: Go into the folder you extracted your CAB to, with all the files out of their directories, create TWO new text files.
For the FIRST text file: name it with the GUID you just generated in step 7 and change the file extension from "<GUID>.txt" to "<GUID>.dsm", press yes to the "Change File Extension" Warning
For the SECOND text file: give it the SAME GUID as above, but change the extension from "<GUID>.txt" to "<GUID>.rgu", press yes to the "Change File Extension" Warning
9: OPEN the "<GUID>.rgu" and select "SAVE AS.." select "UNICODE" (Default is ANSI), then go to the "Save as Type" Menu and select "All Files" and select your "<GUID>.rgu" and select "Yes" to the "Are you Sure You Want To Replace" warning
10: Go back to CABManager.exe and select the "XML" button, and a new window will pop up. In the new window select the tab "Registry Keys"
This will show you all of the REG Keys related to that CAB (If there are any, sometimes the software doesn’t need any so there will be nothing here!!)
Assuming that there are REG Keys, copy them all into the "<GUID>.rgu" and save it, REMEMBER TO SAVE AS "UNICODE"
Next you MUST make sure that the following is in the "<GUID>.rgu"
A: TOP LINE MUST say "REGEDIT4" (no ""), followed by a blank line, eg to follow:
[HKEY_CURRENT_USER\Software\HTC\Customize]
"Ver" = "1.0"
this must change to:
REGEDIT4
[HKEY_CURRENT_USER\Software\HTC\Customize]
"Ver" = "1.0"
B: Go to the end of the "<GUID>.rgu" and ensure that after the last line of text there is another blank line
AFTER you have edited the "<GUID>.rgu" with the correct things, SAVE IT AS "UNICODE"
11: 1: Download this "option.xml" from Rapidshare or SendSpace
Open the "option.xml" and edit the bits that need editing.
you will see what I mean, as I have created the option.xml to be self explanatory!!!
I hope this helps, if you have any questions PM me
OEM folder of HTC rom here: form pof
Kaiser dump thread
http://rapidshare.com/files/42085076/KAISER_OEM.7z.html
P.S. i would live to see the apps ported but when i try to cook even known stuff i get errors and discuraged so i stop
i am on vp3G's Vir. 3.0 it is what i need until someone puts something i can use up.
thanks to the cooks, and things that make you say huummmm

In case somebody is searching the cab-manager now ;-)
http://forum.xda-developers.com/showthread.php?t=317358

Jesus, do none of you read anything any more? I don't like "n00b" bashing but when there's so many of you who have obviously read absolutely f*** all, then I'm thinking you're all fair game.
There are already LOTS of threads about ROMs with the Kaiser comm manager, dialler etc built in - there's been god knows how many attempts to get touchflo working, cooking in kaiser's touch.dll, hacking the old one, creating new ones, all about why you can't flash another device's ROM on to a hermes - mulitple threads about every damn thing you've been talking about, some of them not even that far away from the front page and none of you have taken the effort to have a look.
FFS, it's like painting a target on your back and going for a walk on a shooting range...

LOL......nicely said Smiffy
It's kinda like "the blind leading the deaf and stupid"....every time a new device hits the shelves, hoards of wombats want everything it has to offer on their old technology...arrgghhh!!!
Mark.
PS. Do you think I could flash the Kaiser ROM onto my Voyager....

Lordsmiff said:
FFS, it's like painting a target on your back and going for a walk on a shooting range...
Click to expand...
Click to collapse
best statement of the year award!

leoiden said:
ok we need members that have created there own cooked roms to give us reallistic insight on how to pull this of?
Click to expand...
Click to collapse
Here is some insite! IT cant be done! you can take certain apps and features from the kiaser rom which has been done many many times if you search for kiaser im sure you will find the home plug in the dail pad and the com manger and im sure some other things but here is a little hint you cant port the touchflow many have tried and come close but it just wont work yet! you can not flash another devices rom to the hermes sorry just wont work.

Lordsmiff said:
Jesus, do none of you read anything any more? I don't like "n00b" bashing but when there's so many of you who have obviously read absolutely f*** all, then I'm thinking you're all fair game.
There are already LOTS of threads about ROMs with the Kaiser comm manager, dialler etc built in - there's been god knows how many attempts to get touchflo working, cooking in kaiser's touch.dll, hacking the old one, creating new ones, all about why you can't flash another device's ROM on to a hermes - mulitple threads about every damn thing you've been talking about, some of them not even that far away from the front page and none of you have taken the effort to have a look.
FFS, it's like painting a target on your back and going for a walk on a shooting range...
Click to expand...
Click to collapse
But seriously, if I cant flash the Kaiser Rom to my Tytn, can I port it into i-phone. Then I won't have any communication devices to post stupid questions again

I hear what you are saying, I actually run a tweaked out Hermes with HTC home (latest version from shen) dialer (older version I don't like the 3g video dialer) and com manager (10 button kaiser) though I use the offical att rom as my base. I have read the threads EXTENSIVELY both here and on other sites 4windows mobile tri-syndicate etc.(Stuff by JJ, Custel, etc.) I've even played with the Touchflo Alpha cab. My question was if it would be possible to take the whole kaiser rom (as opposed to extracting portions of it and loading them into one of the hermes roms) and load it on to a hermes, mainly because the issue (from what I have read) with touchflo is the touch.dll file and how it functions (wizard, kaiser, and elf similar, heremes is different) and this dead ends most projects. I was thinking that perhaps flashing the whole ROM might get around this (basically try to run a kaiser on a hermes, I was hoping that the devices were similar enough it might work). I guess the answer is no. The other thought I had was that perhaps the new offical release might be easier to work with (and the business card app is pretty sweet). I am somewhat technical but not a developer (though I work for for a large development firm) perhaps I misunderstood how a rom works and flashing the entire thing will not be posible nor will it solve any of the issues the chefs have been running into. It was just an idea.

aaronsmckee said:
I hear what you are saying, I actually run a tweaked out Hermes with HTC home (latest version from shen) dialer (older version I don't like the 3g video dialer) and com manager (10 button kaiser) though I use the offical att rom as my base. I have read the threads EXTENSIVELY both here and on other sites 4windows mobile tri-syndicate etc.(Stuff by JJ, Custel, etc.) I've even played with the Touchflo Alpha cab. My question was if it would be possible to take the whole kaiser rom (as opposed to extracting portions of it and loading them into one of the hermes roms) and load it on to a hermes, mainly because the issue (from what I have read) with touchflo is the touch.dll file and how it functions (wizard, kaiser, and elf similar, heremes is different) and this dead ends most projects. I was thinking that perhaps flashing the whole ROM might get around this (basically try to run a kaiser on a hermes, I was hoping that the devices were similar enough it might work). I guess the answer is no. The other thought I had was that perhaps the new offical release might be easier to work with (and the business card app is pretty sweet). I am somewhat technical but not a developer (though I work for for a large development firm) perhaps I misunderstood how a rom works and flashing the entire thing will not be posible nor will it solve any of the issues the chefs have been running into. It was just an idea.
Click to expand...
Click to collapse
Touch.dll on a kaiser wun work on hermes... Datz the problem

If at first you don't succeed then make the target BIGGER!

What was that that LordSmiff said? It was sooo long, I couldn't read the whole thing.
Oh never mind. I forgot, I wouldn't bother reading your answer, either.
Can somebody pleeeeaaaasssseee make a video of alll this stuff on the forum. I can watch TV ok.
Anyway ... I just pre-ordered my Kaiser. Is there any way to flash my Hermes ROM onto it so I don't need to learn anything new?
Puuullllleeeeaaasssse help me!!!
Oh, and my keyboard makes a ? whenever I type a *. Haven't seen anything mentioned about this problem here.
-pvs

pvs said:
Oh, and my keyboard makes a ? whenever I type a *. Haven't seen anything mentioned about this problem here.
Click to expand...
Click to collapse
I had this problem. Use HTCustom and go all the way over to the "keyboard" tab and choose the correct one (I have AT&T/Cingular, so I chose that).

mcorrie1121 said:
I had this problem. Use HTCustom and go all the way over to the "keyboard" tab and choose the correct one (I have AT&T/Cingular, so I chose that).
Click to expand...
Click to collapse
Ummmm ... I was being a little sarcastic. Yes, I know ... it's just one of the questions that's been posted a few thousand times already ... probably will be again tomorrow.
Thanks for answering, though.
-pvs

[TUT]ROM for everyone (video tutorial to cook the ROM )

Hi all
I was looking for the way to cook my own ROM. There is a heaps of info for a Kiser but not a Diamond. I had decided to start a thread that will show and explain in plain language how to do it on the Diamond. The aim is to have perfectly clean ROM without any unwanted applications or tweaks. The ROM will only contain bare minimum to run PDA. Everything else can be installed with cab files. Also registry tweaks can be applied after installation.
What is more important I want this thread to be a simple to follow guide to cook a ROM so everyone can make one for themself. Since I’m not an expert I welcome any help from anyone.
I had managed to cook my 1st ROM. I had removed some applications without modifying anything else.
I have tested it and it worked ok. However you perform it on your own risk and I take no responsibility if you stuff it up. Do not remove everything at once. Remove 2-3 application and see if it works. If yyou unsure just leave it alone. When you are confident you can remove the rest of apps. Also if you want to remove Opera and TouchFlo you need to change a setup files so lets leave it for now.
You need a Kitchen and the ROM file.
Video Tutorial (rigt click and Save target as)
Extract kitchen files directly to C drive (not to desktop as shown on the screen shot)
IMAGE
Extract rom files into BaseROM folder in the kitchen.
IMAGE
Open !BEGIN and choose option 1
IMAGE
Just follow the prompts and press ENTER when asked. When you get to screen below just wait till asked to press ENTER again. This might take a while.
IMAGE
When you arrive to this screen
IMAGE
your rom preparations are complete.Hit the ENTER to close window.
Go to Kitchen folder and you notice that rom files and packages are extracted.
IMAGE
To remove unwanted applications from rom look into OEM and SYS folders. You need to delete all folders related to paticular application. (create separate folder and move all packages there instead deleting. Later on you can convert them to .cab files and install them if needed)
IMAGE
If you have some cab files and would like to add them into the rom you will need THIS application. Just start it, make sure that Remodule option is deselected, open cab file and program will create new folder containig packagage file. Make shure that PACKAGE_Diamond_ is in front of the filename. For example if you converted TomTom cab you should rename it to PACKAGE_Diamond_TomTom. Now copy the folder to OEM folder in the kitchen. Repeat process till you add everything you would like to have in the ROM.
When you delete/add everything you want start !Cook file
IMAGE
This will start OS building application. Just hit a green button and wait till it finishes. It will create os-new.nb file needed later. Close window on top (never close a DOS window) and rom building application will start.
IMAGE
Fill all the info as shown on the screenshot.
IMAGE
Use apropriate version rom (ie FR, ME etc...). As for the system select os-new.nb which is in the kitchen folder. Also you can select boot images and radios but for now we leave as it is. When ready hit Build ROM button.
Name your new rom (anything you want).
IMAGE
And hit SAVE.
A while later you should see screen below
IMAGE
Hit OK. Wait till everything finishes. Just press ENTER when asked. On the end you get message that rom is ready to flash. Hitting ENTER closes a window. All you need to do is flash it to your device.
PS Everyone is welcome to help. I need information how to update Framework and OS and where I can download it. Please post suggestions, registry tweaks and links to updated cab files for the apps removed from the rom. I will make a video tutorial after I have all info needed. I want to make easy for everyone who wants to have personalized rom.
Credits: Thank you to all who provided these great tools and these that helped in this thread.
EDIT: If you manage to create your own ROM please do not flood forum with new ROMs (unless it is something we never seen). There are experienced cooks that created really nice ROMs. Lets keep this forums clean.

There is a thread in this forum which has a simple to use kitchen. Using it is just easy as Steps 1-2-3.. But it doesn't work for some ROMs, atleast for me. By far, it is a great tool simplified in batch files.
Are you using the same tool or your own customised one?
Regards,
Carty..

lolek74 said:
Hi all
I was looking for the way to cook my own ROM. There is a heaps of info for a Kiser but not a Diamond. I had decided to start a thread that will show and explain in plain language how to do it on the Diamond. The aim is to have perfectly clean ROM without any unwanted applications or tweaks. The ROM will only contain bare minimum to run PDA. Everything else can be installed with cab files. Also registry tweaks can be applied after installation.
What is more important I want this thread to be a simple to follow guide to cook a ROM so everyone can make one for themself. Since I’m not an expert I welcome any help from anyone.
I had managed to cook my 1st ROM. I had removed some applications without modifying anything else.
I'm off to bed now. I'll post screenshots and info tomorrow. Please register your interest.
Click to expand...
Click to collapse
Could do my... i just finished my one yesterday a perfect clean rom not staffed wth litter....i used the surface kitchen and based on ce 0s 5.2 20273 wwe a bit customized the manila that's all....

Is it a clean ROM with most apps removed? Do you want to share please.

Good initiative!
I really want to know what is the true performance of the Diamond, running it with just the minimum required.
Even when disabling TF3D and other extras, I find it so slow compared to other WM phones having less MHz... I just don't understand why.

Uploading my ROM now. It is slow. I will post the link tomorrow.

Just a tip, A clean rom is very good if you going to stick with what you got in the rom and possible a few otther apps by cabs, If your going to installed the same apps which are in a full rom then the clean rom with those apps in will make you lose valuable storage space rather than them cooked in and sometimes device will start to feel sluggish but it all depends on how many cabs youre going to re-install.
TIps , there are certain apps which are cooked in doesnt take up any storage space but if install by cab you will then use up valuable space.

duttythroy said:
Just a tip, A clean rom is very good if you going to stick with what you got in the rom and possible a few otther apps by cabs, If your going to installed the same apps which are in a full rom then the clean rom with those apps in will make you lose valuable storage space rather than them cooked in and sometimes device will start to feel sluggish but it all depends on how many cabs youre going to re-install.
TIps , there are certain apps which are cooked in doesnt take up any storage space but if install by cab you will then use up valuable space.
Click to expand...
Click to collapse
Really? Dutty, could you please explain that a little bit further? Don't we have a set amount of storage space? i.e. If you cook some apps in, then you lose some of that space. If you add them later, you lose some of that space. But at least you could uninstall them.
So please correct me if I have misunderstood and I'm only guessing, but are you saying there is a part of the ROM that is only available to the OS 'image', and cannot be accessed in the normal way once the device is up and running? And are you using that space to install some apps? If so, how much space in the 'OS image' part of the ROM is available for that purpose? I would like to start cooking my own ROM's, but I don't want to waste ANY storage space that I am not forced to.
I would really appreciate if you could shed a little light on that for me! Cheers

Thanks, this is great.

salada2k said:
Really? Dutty, could you please explain that a little bit further? Don't we have a set amount of storage space? i.e. If you cook some apps in, then you lose some of that space. If you add them later, you lose some of that space. But at least you could uninstall them.
So please correct me if I have misunderstood and I'm only guessing, but are you saying there is a part of the ROM that is only available to the OS 'image', and cannot be accessed in the normal way once the device is up and running? And are you using that space to install some apps? If so, how much space in the 'OS image' part of the ROM is available for that purpose? I would like to start cooking my own ROM's, but I don't want to waste ANY storage space that I am not forced to.
I would really appreciate if you could shed a little light on that for me! Cheers
Click to expand...
Click to collapse
bascally there some programs which ar cooked in for e.g Remote desktop, If cook this in its 1.45mb I think, I will only use up only about .45mb and save 1mb of storage space, If i install this by cab I would use up all of the 1.45mb storage space

Perfect
I was hoping/loocking fopr a thread like this! BUT
Could anybody explaine to me how to dump a rom?
The one I am using right now is pretty good and I want to modify
it and loose all the unwanted programs...
But what happens to all the .cab programs I have installed at the moment?
Do they "get dumped" as well so I can preserve them as OEM? Or do I only dump the "base ROM"?
And what about the Reg tweaks? Do they get dumbed aswell?
Thanks for the help...

bascally there some programs which ar cooked in for e.g Remote desktop, If cook this in its 1.45mb I think, I will only use up only about .45mb and save 1mb of storage space, If i install this by cab I would use up all of the 1.45mb storage space
Click to expand...
Click to collapse
Thanks for the reply, so what is the reason behind that... How can that 1MB be shaved off? Is it compression?

duttythroy said:
bascally there some programs which ar cooked in for e.g Remote desktop, If cook this in its 1.45mb I think, I will only use up only about .45mb and save 1mb of storage space, If i install this by cab I would use up all of the 1.45mb storage space
Click to expand...
Click to collapse
And to top this, apps that are cooked run faster than an installed cab.
But for some, a ultra light rom works becouse they have not ,uch progs to use, and need to install less cabs.
gr.

Just a short notice, lolek:
I see you've extracted the kitchen to your profile folder.
You'd better extract it to the root of your drive, like C: or D:
batch files have a tendency to disliking spaces in file/folder names as well as names longer than 8+3.

surface_rom said:
And to top this, apps that are cooked run faster than an installed cab.
But for some, a ultra light rom works becouse they have not ,uch progs to use, and need to install less cabs.
gr.
Click to expand...
Click to collapse
exactly also if you look at some of the benchmarks as well the lite roms are not much better or even some of the full roms are faster, so its all about what u really need in the rom, if your going to install everything back in your rom with cabs, its better to go with a full rom

Thanks for the input. This is what I was hoping for. The aim is to have simple tutorial for anybody to create their own ROMs. I'm off to work tonight but I'll update 1st post tomorrow.

I have updated 1st post. It shows how to convert cab files to packages and add them to the rom. I apologize for the slow progress but I'm still learning myself.
I have asked around how to update framework and OS. As soon as I get reply and test it I’ll post it here.
I know there many experienced cooks so please don’t be shy and help create this guide.
When guide is complete I’ll make movie showing whole process.

lolek74 said:
I have updated 1st post. It shows how to convert cab files to packages and add them to the rom. I apologize for the slow progress but I'm still learning myself.
I have asked around how to update framework and OS. As soon as I get reply and test it I’ll post it here.
I know there many experienced cooks so please don’t be shy and help create this guide.
When guide is complete I’ll make movie showing whole process.
Click to expand...
Click to collapse
very nice man, keep it up!

this is very good idea to put together a tutorial to cook the ROM! cant wait to cook my own ROM with this.
thanks a lot man!

Having a Slight problem with the surface kitchen.
During the process of extracting a rom at the stage of '2a.ExtractDumpIMGFS.cmd'
'Recmod.exe' crashes.'
anyone know why and how i can solve this?
Thanks in advance

[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

HP iPAQ 21x Custom ROMs-Help Needed!

Hello, I'm new here, and I have been attempting to make two custom ROMs for the HP iPAQ 21x series, and I ran into a huge problem. I have two dump folders, and I can't figure out how to turn either of them into an NBH(or NBF) file. Any help would be highly appreciated.
Edit:Oh, and also, in case anyone was wondering, I'm trying to make them a Windows Mobile 6.1 ROM and a Windiows Mobile 6.5 ROM, and they are both(as far as I know) clean, except for the HP stuff.

nbh or nbf... ? for what ? it is inpossible to flash it back, you need bldiag.nb0 and hpimage.bin (foxconn format) but fortunatly pdocwrite works fine, so you need to: dump or download dump of imgfs (part02, os) unpack it via imgfstodump, cook to wm 6,1 or 6.5, then convert back to imgfs via imgfsfrom dump, and write via pdocwrite, xip can be also writed by this way, xip is part01, it works but i'm not a rom cooker so I cant cook it myself...
edit: it is also possible to edit marvell obm's and bootloader, but only via linux
edit2: here is my post about ipaq 214 and pdocwrite http://forum.brighthand.com/showpost.php?p=1762892&postcount=4
edit3: it will also works on any 21x and 11x and as I think on other hp devices manufactured by foxconn

I'm sorry elektrownik, but I don't really get what you're saying, I'm not very experienced with this ROM stuff, this is the first time I've ever tried to make one. But in response to what you're asking(I think), I was going to make them NBH files, make a backup ROM image of the device, and then use the HP RUU, which I have made to look for a file called 'RUU_signed.nbh'(what I will name them), to update the device via Activesync connection.

Update:OK, I've managed to get a little further, and now I have two BIN files, and two NB.PAYLOAD files, and I'm pretty close to turning them into NB Files.

But how do you want to sign it for hpruu it need hp cert and key, or did you cracked it. Anyway here is default rom. http://rapidshare.com/files/2236847...n_marked_internally_with_custom_extra_data.7z

Oh, well I didn't know it had to be signed, but in the ROM files which I was basing mine off of(which I thought you made) was an HP digital signature file(.cer) that said it went an HP 21x Image Update, I clicked on it, Windows said it installed the certificate, and then the file dissapeared. I'm not sure if that will help use the HP RUU or not, but I found it kind of odd. Also, if you'd like to take a look at it I can put it up for download somewhere(there was another one).

Fdo35 said:
Oh, well I didn't know it had to be signed, but in the ROM files which I was basing mine off of(which I thought you made) was an HP digital signature file(.cer) that said it went an HP 21x Image Update, I clicked on it, Windows said it installed the certificate, and then the file dissapeared. I'm not sure if that will help use the HP RUU or not, but I found it kind of odd. Also, if you'd like to take a look at it I can put it up for download somewhere(there was another one).
Click to expand...
Click to collapse
just do what I wrote - cook wm 6.1 or 6.5 to romdump convert it back to imgfs and it will be posible to write it to device by pdocwrite application

Fdo35 said:
Update:OK, I've managed to get a little further, and now I have two BIN files, and two NB.PAYLOAD files, and I'm pretty close to turning them into NB Files.
Click to expand...
Click to collapse
What parameters did you use for Tadzio's imgfs tools on NBSplit?

Fdo35 do you know how to flash ipaq 21x?
Maybe you can work together with some people already trying to make wm6.5 rom....
Kind regards,
W.

Steven855 said:
What parameters did you use for Tadzio's imgfs tools on NBSplit?
Click to expand...
Click to collapse
What's "parameters", I don't know what you mean. Also I don't remember using NBSplit, I started out with a IMG file which I then dumped.
Edit:Oh wait, I see what you mean. I didn't use NBSplit, I was following the attached directions to reconstruct ROM, except it wasn't for the device the file specified, and instead of 'imgfs.bin', I used a file called 'ipaq214.img', and instead of 'Windows.nb' I used a file called 'flash.nb'. And, I'm pretty sure that elektrownik made both files.

lol why you all dont read what i wrote, i have rom, which was reconstructed from dump, but it impossible to flash it from sd like on htc by flash.bin, ipaq 214 need bldiag.nb0 and hpimage.bin to be flashed from sd, but those files never was released so it is impossible to study format in which they coming, 214 can be also flashed from pc, but it need foxconn application and like before hpimage.bin, and there is official metchod - hpruu, but files which it use need to be signed first, we dont have cert and key to sign them, it wold be possible to patch hpruu to delate sign validation but i dont see anyone who working on this, as i wrote only one working metchod is pdocwrite application, i check it and it works, but i'm not room cooker so i cant cook wm 6.1 or 6.5 imgfs...

I think there are quite few topics about it.
It would be maybe better to have EVERYTHING relevant in one so everyone who posesses knowledge can help.
Now it looks that we (you) are inventing hot water... no offence - i appreciate all the hard work you put into this. But we (you) need better cooperation and clean topic.
I am grateful to everyone who share and try to make something. Respect to you all!
Kind regards,
WODP

The HP iPAQ 110 has a ROM update on HP's website, is it possible to get any of those files from that?
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=215348&prodSeriesId=3644061&prodNameId=3644062&swEnvOID=4014&swLang=13&mode=2&taskId=135&swItem=hh-59617-3

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