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

[PRJ]Start Kit. Kitchen. Based at official stable release (479.3WWE). UC Ready.

Just start kit. For further cooking.
Based at official release (and stable, I hope,- don't like to be beta-tester for HTC "in the dark").
It's new way for me (just began to use WinMob by Diamond), so don't bite me too much
Don't forget about Hard-SPL!
Few cosmetic changes & a little tweaked. UC ready.
In OEM left TouchFlo only.
In SYS out: OneNote, PowerPoint, WindowsLive, Help & other rubbish.
In "Install" folder - example only. You can change it to your own provider (look to OEM\CONNECTIONSETUPDB - password I found at XDA) or just use ConnectionSetup.
The most tweaks - in OEM\xxxconfig
Be careful to finish.xml - it's important file!
(return to "Internal Storage". Manila start including in this file too. You can customise it up to you. Same as *.rgu in this folder)
To find the bugs&errors better together, I think
Ideas&remarks - welcome!
It's OPEN PROJECT.
Kitchen: http://rapidshare.com/files/143594363/WWE_1.93.479.3_kitchen.zip
Example ROM (with pass for provision.zip):
http://rapidshare.com/files/143600258/1.93.19965.Light.rar
For make the same - just press !COOK.CMD in the kitchen.
Lighted packages:
http://rapidshare.com/files/144298572/PACKAGE_Diamond_PhoneCanvas.RAR
http://rapidshare.com/files/144138802/PACKAGE_Diamond_QuickGPS.RAR
The trick - in change heavy bmp files to compressed/indexed png.
And patched dll/exe, for use another files.
Not sure about using system resources in this way - up to you. Try.
Changes: http://rapidshare.com/files/144298443/changes_to_kitchen.rar
(Corrected ROM container: 19965 now. Was 20273 - just mistake. And help engine)

can I just install your rom on my Diamond?
Would like to try it, but dont want to fool around with the Kichen stuff

Been reading much on cooking the last days. This looks like a good start!
Thanks for sharing. Hope I can create my own Diamond ROM from here. If it's good enough for some of my friends I will share it on XDA as well

teddyen66 said:
can I just install your rom on my Diamond?
Click to expand...
Click to collapse
Not see the reason - only base functions.

You are right, but it's the fastest ROM I've ever tried
But like you said, it's very basic. Camera is not working, so you need to add all these yourself.
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
It does seem to extract just normal. Is the RAR file save?
update: You might even remove the Office part from the light ROM??

mccune said:
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
Click to expand...
Click to collapse
Hm. "Top" level - zip. Inside - rar. Going to try download back. May be corrupted...
No, everything OK to archive.
I use rar v.3.71
mccune said:
You might even remove the Office part from the light ROM??
Click to expand...
Click to collapse
Word & Excel till alive

mccune said:
You are right, but it's the fastest ROM I've ever tried
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
It does seem to extract just normal. Is the RAR file save?
Click to expand...
Click to collapse
Its 7-Zip i think extracts ok

I will give this a try, other kitchens didn't work out for me very well.
Thanks man ...

Help system
I think idea to remove the help system absolutely is not the best.
Sometimes apps need it for normal work. May keep help engine alive?
Any opinions?

Please tell me one usefull hint that's provided to you because of the Help function?
For me it's wasted space on every device I've owned. If I encounter any problem they go beyond the help files

Looks pretty complicated with no real guide, will look into other kitchens!

I talk about engine (hwhelp) only. The most help files - "dead cargo", of course.
After try to push "help" button at some apps - error, could make system unstable.
P.S. made two "light" packages. ( see in the first post).
It use a little less memory, I hope.

Congratulations for this new project! If you need any help about a multilanguage (Italian) version... I'm ready!

sev7en said:
Congratulations for this new project! If you need any help about a multilanguage (Italian) version... I'm ready!
Click to expand...
Click to collapse
Thanks for support
I think, change the locale - it's only change the *.mui & may be other files in folders *_0409. Change to Italian locale - _0***, don't know exactly.
Could you try it?

Found the mistake - "alien" rom container (from 20273) in the kitchen.
Just accident.
May be it's nothing, but...
- in the first post + hwhelp.exe: changes_to_kitchen.rar

Tricks
Stop unused services (functional don't loose) - will start on demand:
[HKEY_LOCAL_MACHINE\Services\BTAGSVC]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\BthAsPlugin]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\BTHIDSVC]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\OBEX]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\QuickGPS]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\WirelessService]
"Flags"=dword:00000004
It's THE SAMPLE. (but I use it)
May stop any more? Biotouch, for example?
------------------------------------------------------------------------
Start HTCVolumeControl.dll without taskmanager, or if you use another TM:
[-HKEY_CURRENT_USER\Software\HTC\BootLauncher\Services\HTCVOLUME]
[HKEY_LOCAL_MACHINE\Services\HTCVOLUME]
"Dll"="HTCVolumeControl.dll"
"Order"=dword:0000000c
"Index"=dword:00000000
"Info"=dword:00000000
"Prefix"="VOL"
Tested on Raphael VolumeControl
------------------------------------------------------------------------

Somebody can explain how to (EXACTLY! step by step) change OS, XIP, SYS in this kitchen? I've read a lot of tutorial but I didn't understand how...
In example, I've got:
1) this kitchen and this "base" rom
2) another diamond rom with 20748 xip build.
If I would to update OS, XIP and SYS to newer, what I have to do?!

GriFolle said:
Somebody can explain how to (EXACTLY! step by step) change OS, XIP, SYS in this kitchen? I've read a lot of tutorial but I didn't understand how...
In example, I've got:
1) this kitchen and this "base" rom
Click to expand...
Click to collapse
You don't neet "base" rom (or what you mean?) it's example only.
If you talk about rom\os.nb in the kitchen - it's just container for rom, which is empty.
GriFolle said:
2) another diamond rom with 20748 xip build.
If I would to update OS, XIP and SYS to newer, what I have to do?!
Click to expand...
Click to collapse
Just delete oem, rom, sys & make you own "tree"

Thanks for your very QUICK reply Modilv!
So, I have just to take the parts of (maybe more) diamond romS that I need (including OS.nb??) and put theme in your kitchen..?
So simple?!
PS: no "porting" xip or something like that?
TIA

It't not "my" kitchen (just add bepe's utility to final step)
I made the "tree" only.
You can do the same.

Looking for infomation regarding cooking roms

Hi to all chefs,
I am looking for as much info on rom cooking as possible as to understand the process that is happening,
what i want to know is when the batch file is run this launches other commands could somebody please explain what is happening behind the scenes
when the buildos runs it processes all the files into a temp folder,
now my most important question is,
when building up the registry, what is the order that the files are processed, by dsm filename? package filename?
also when are the mxip_******.provxml files processed (reg esttings added to the registry and in what order
how is the best way to add a custom mxip_****.provxml to garantee my setting don't get changed,
also if there is enough useful answers posted, i will edit this post to make a time-line in post2 to help others new to cooking there own roms,
then infos wanted for timeline are the background into whats happening in each program launched (buildos,nbhtool etc) from pressing the cook batch file through to windows being flashed and autorun kicking in, sdautorun if exists, then the end would be the final reset and windows ready to use,
hope you will make useful answers
many thanks.

Reserved for timeline
timeline
1 cook button pressed
1.1 BuildOS launches
1.2 G'Reloc launches
1.3 NBSplit -kaiser OS.nb
1.4 ImgfsFromNb OS.nb.payload imgfs.bin
1.5 ImgfsFromDump imgfs.bin imgfs-new.bin
1.6ImgfsToNb imgfs-new.bin os.nb.payload os-new.nb.payload
1.7NBMerge -kaiser os-new.nb
1.8 HTCRomTool.bat
1.9 DiamonCustomRUU.exe
1.10 Cleanup.bat

garymeg said:
Hi to all chefs,
I am looking for as much info on rom cooking as possible as to understand the process that is happening,
what i want to know is when the batch file is run this launches other commands could somebody please explain what is happening behind the scenes
when the buildos runs it processes all the files into a temp folder,
now my most important question is,
when building up the registry, what is the order that the files are processed, by dsm filename? package filename?
1. the *buildos*.exe generates logfile with order
2. you can minimize the number of dsm-files/packages by your self.
i.e OEM, Packages and SYS to one dsm/rgu/provxml
also when are the mxip_******.provxml files processed (reg esttings added to the registry and in what order
mxipCOLD at coldboot (first time/only one time)
mxipUPDATE at resets (allways)
how is the best way to add a custom mxip_****.provxml to garantee my setting don't get changed,
"your device will ... in 3 seconds ... 2 seconds"
also if there is enough useful answers posted, i will edit this post to make a time-line in post2 to help others new to cooking there own roms,
these are not usefull answers, but iam to tired for details but i cant write nothing ...
then infos wanted for timeline are the background into whats happening in each program launched (buildos,nbhtool etc) from pressing the cook batch file through to windows being flashed and autorun kicking in, sdautorun if exists, then the end would be the final reset and windows ready to use,
hope you will make useful answers
many thanks.
Click to expand...
Click to collapse
generaly the kitchen/device that you use and/or how much detaild you have cooking-knowns will determines the order.

I Know very little, i can take a rom add packages and rebuild, thats my limit, i want to create this thread so i can better understand what is happening, edit files, make sure my edits dont get changed later during the setup process, I would think this applies to most devices (i have a diamond and also Artemis) the kitchen i use is the modifyed kiaser kitchen as when i was modding artemis i found a simular kitchen for that device and a lot of my packages were reused.

for extracting artemis i use the hypercore-kitchen. but for cooking i changed to ARTEMIS_DEV_v2.1_Build_19199-kitchen. the reason is, that the file-structure in hypercore dismis/damages my brain.
for diamond i use the "kitchen"-kitchen (orig. download filename was kitchen.rar).
ohh, its ringing, so i have end again ...
p.s.
study the system.txt inclusive the batch-files together with the batch-files from "kitchen"-kitchen.

Samsung SGH-i780 (and any other WM device for that matter!): Learn how to cook ROMS

Hi guys,
I decided to open a blog which explains how to cook roms for the i780. There are very few chefs, and cooking is a really hard science to learn without help! So, I decided that I take the time and write posts so that everyone could learn the process in a methodical manner and cook roms in the future!
I'd slowly write posts explaining each step of the process in detail, so that we can have more people learning how to cook and make the i780 community more happening
Head over to this URL to check out the first few posts -
http://i780romdev.blogspot.com
Update:
Attached core kitchen tools that you'll need to use! Enjoy!
cheers
San

I never was a fan of this forum, not sure why, maybe because I use a ASUS P527 and there are not proper instructions on how to create a custom ROM, I appreciate your taking the initiative

I think its good fun to try and figure out things on your own
Non-HTC devices do have a very small fan base unfortunately....and ironically, HTC makes the crappiest devices imo (highly crash prone, buggy, lousy drivers, useless qualcomm processor)!
You can apply the same tools and techniques even to cook asus roms....its not all that different
cheers

wooooooow thanks a lot buddy finally we have it also !!!

when will u release part 3? and also can u give the links of programs? like pkgtools_? coz i tried to download it from somewhere else and it had virus

benveq said:
when will u release part 3? and also can u give the links of programs? like pkgtools_? coz i tried to download it from somewhere else and it had virus
Click to expand...
Click to collapse
hi m8!
i'll try and upload the set of tools shortly. You can get it in any of the kitchens posted for the i780 here. I'll however consolidate them and add it in this post as an attachment!
Part 3 - very soon
cheers!

You guy thanks for sharing your experience at cook ROMS,I whink I need this for my SmartPhone.

Hey guys, just dropped the next part of the series on the blog. Check out http://i780romdev.blogspot.com
Of course, the same theory, tools and understanding goes to cook for any other device too
cheers

kitchen tools attached in the first post.
enjoy

dreamtheater39 said:
Hey guys, just dropped the next part of the series on the blog. Check out http://i780romdev.blogspot.com
Of course, the same theory, tools and understanding goes to cook for any other device too
cheers
Click to expand...
Click to collapse
yeah, now i am reading part 3 and u really teach very well! i think i will cook my own room soon with ur help i wanna ask a question if i dont want ms office and internet explorer in my rom which folders should i delete? i wanna add different office program

benveq said:
yeah, now i am reading part 3 and u really teach very well! i think i will cook my own room soon with ur help i wanna ask a question if i dont want ms office and internet explorer in my rom which folders should i delete? i wanna add different office program
Click to expand...
Click to collapse
To remove a package, you can get rid of the corresponding folders in your SYS folder. But its not recommended that you knock off office/ie as they might be referenced within other apps. You can always take it off, build a rom and see if everything works fine
For example, to remove IE, just delete your Browsing, Browsing_DPI_xx and Browsing_Lang_XXXX, BROWSINGCORE, browsingie, browsingie_LANG_XXXX folders. That should get rid of IE for you! Then you need to recreate your bin!
cheers

thanks a lot for kitchen tools and ur explanations! i read ur blog all the time great work!!

The next post is up
cheers

dreamtheater39 said:
The next post is up
cheers
Click to expand...
Click to collapse
yes i read it, and u r teaching with examples it is great

i have two problems while i am using ervius pkgtools
1. when i open dumo folder it shows
[Missing Manifests]
(Maybe):\ROM\XIP\45116509-e364-4775-9098-c25f0b1fbac2.dsm
(Maybe):\ROM\XIP\d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
(Maybe):\ROM\XIP\723fb954-d931-4348-b672-82a188e587b5.dsm
(Maybe):\ROM\XIP\1a22bb67-d4c4-7bb4-c5d2-75cb3a85c45b.dsm
(Maybe):\ROM\XIP\449da4ef-e9c1-5cb4-2ec5-fb9b4c27a865.dsm
are these important dsm files?
2. when i press build packages it gives this error:
not found: select .os file to extract XIP
and i extract xip file using osbntool as xip.bin
any solutions for both of these?

benveq said:
i have two problems while i am using ervius pkgtools
1. when i open dumo folder it shows
[Missing Manifests]
(Maybe):\ROM\XIP\45116509-e364-4775-9098-c25f0b1fbac2.dsm
(Maybe):\ROM\XIP\d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
(Maybe):\ROM\XIP\723fb954-d931-4348-b672-82a188e587b5.dsm
(Maybe):\ROM\XIP\1a22bb67-d4c4-7bb4-c5d2-75cb3a85c45b.dsm
(Maybe):\ROM\XIP\449da4ef-e9c1-5cb4-2ec5-fb9b4c27a865.dsm
are these important dsm files?
Click to expand...
Click to collapse
This is not important....ignore them, its normal
benveq said:
2. when i press build packages it gives this error:
not found: select .os file to extract XIP
and i extract xip file using osbntool as xip.bin
any solutions for both of these?
Click to expand...
Click to collapse
When you start, it asks if you would like to run build xip.bat.....just hit NO for that....

trojan reported in the attachment
Win32/TrojanDownloader.Zlob.NBP
false alarm?

well last night i finished my own wm6.1 build 20270 128dpi pdxib1 according to your guide i wanna tell what i did to complete it ;
1.i exctracted my rom using i780 kitchen and i got dump folder and i also added some extra tools like ervius buildos,osnbtool etc...then i used pkgbuildos to seperate folders into oem and sys
2. i used oem part from krizky82's kitchen and i add some extra packages using ervius package creator 2.7 and add them with oem_blahblah to oem folder.
3. i deleted windows live and msn messenger from sys folder and copied netcf 3.5 and flashlite v3.1 from krizky82 kitchen. i also used his initflash and rgu file coz i had same structure almost(oem totally same and sys programs also)
4.i looked at both efn's kitchen and krizky82 kitchen and i saw that they have this structure oem,sys and rom and in rom there is xip folder. when i looked at inside xip folder i saw that there is only coredll.dll folder and others are dsm rgu and boot files so my next step
5. i used osbn tool to exract xip.bin and after i got that xipkitchen_beta6 and i choosed the same donor and original and after extracting i got original xip files and i ordered in same structure like efn's kitchen
6.then i used pgkbuildos and let the process starti had some dsm duplicate errors and i delete duplicated ones and later i didnt start xip extract bat and flashable bin bat so after process again i had temp/dump folder
7. during buildos there wasnt any error and i was happy about it
8. using inputTXTFileMaker ( thanks to u dreamtheather93) i got input text and after that using these commands;
mgfsfromdump imgfs_raw_data.bin new_imgfs.bin
del imgfs_raw_data.bin
ren new_imgfs.bin imgfs_raw_data.bin
make_imgfs i780.nb0.payload.body -nosplit
merge i780.nb0.payload.header i780.nb0.payload.body i780.nb0.payload
nbmerge -data 2048 -extra 8 i780.nb0 -conservative
and conv3 input.txt > conv3_output.txt
ren i780.nb0.b000ff !!i780_flashable_bin.bin
i got my flashable bin file yupiiiii i controlled the size of flashable bin and it is 86.2 mb and the size of dump folder almost 125 mb i hope it is ok
now i will flash my phone but is there any possibility that my phone can be bricked ?
thanks a lot for ur guide again!!!
note: i already used i780.bin as 12mb page pool size i did it before kitchen using osbn tool

good job m8
You cant really brick your i780 because of this I've done way crazier stuff....like trying out omnia's xip, drivers of omnia on i780....and nothing's given way
However, i'm hoping you've ported your XIP accurately, and i'm unsure how've you've built your SYS folder.
but, go ahead and flash and see if it boots nothing to be paranoid if it doesnt boot/hangs at startup/throws an error and fails etc. etc. If any of this happens, then we could troubleshoot it together
cheers & good luck

Great job!
Nice start San!
Not even some days left from your first successful cooking and you already best gid on it!
Keep on do it. And we wait for new mods for our best touchphone!
I think now anyone is able to break Eagles wings =P

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