Related
FOREWORD:
I would like to keep this thread EXPLICITLY for people who want to learn how to MANUALLY cook and the questions surrounding the topic.
If you are a "GOD MODE" and you are more interested in insulting people for trying to learn DONT read this thread
n00bs DO YOUR RESEARCH!! - See links in my Signature and at the bottom of my second post
If you are answering a question PLEASE answer it fully and as simply as possible.
WELCOME TO ROMDonalds!!!!!!!!!
This kitchen is designed for those users, like me, who have been using their devices for a while and want to learn the methodologies behind hand cooking a ROM. By hand cooking I mean manually adding OEM software, adding CAB’s so they don’t have to be installed after flashing, hand editing registry hives and such like.
Don’t get me wrong GUI kitchens are excellent but, to fully understand the processes that go on behind cooking your own ROM,I feel that it should be done manually so you can see and hopefully understand what happens at each stage, so you could say that this is more of an educational kitchen.
.
.
How It Works
There are various stages to cooking a ROM, so when you run “ROMDonalds.exe” you will find a group of files, ordered by number, logically, you start at number 1, and follow the process through to completion.
After running “ROMDonalds.exe” you will find a new folder on your desktop called “ROM Donalds” this is your kitchen.
Inside each of these files are all the various pieces of software you will need to complete that particular stage of the process in addition to this there is an instruction manual that walks you through each step, with background information on what is happening not just the required steps.
.
.
The Kitchen Software
All of the software in this kitchen is available in other kitchens in various forms, some of the software has been slightly edited from original form but not by much, so I do not profess to having produced some revolutionary cooking software as it all currently exists.
The difference is that instead of having a folder full of tools with strange looking names, which would be intimidating and confusing to a new user, everything is sectioned out with instructions.
.
.
Thanks:
Special Thanks to Midget_1990 for helping with the software
Thanks to all those who originally designed the softwares used in this kitchen, namely:
Tadzio - for his tools
bepe - for his tools
the-equinoxe - Splash Screen Tools
dutty - NBH Tool
also thanks to anyone I forgot (sorry about that!)
.
.
Disclaimer
I accept no responsibility for devices getting screwed!!
.
.
Download Links :
In the second post of this thread you will find all the required download links, patches and Instruction Manuals, detailed as follows:
ROMDonalds Kitchen : This is your base kitchen
Animated Startup Screens : A pack of various animated startup screens
Selection Of OEM Apps: A large selection of pre-created OEM packages ready for cooking
.
.
Download Links
Release Notes :
1) If you find any errors with the instructions please detail them in the thread, but also PM me with the error and necessary changes so I can update the "How To Cook.pdf"
2) This has been tested as much as possible on Vista and XP and fully works on both (for me!!)
3) Section in "How To Cook.pdf" on converting CAB to OEM needs refining, if you are new to this ignore the section and just use the OEM apps i have included until i make this section better
4) There is a folder in ROMDonalds called "09-AdvancedTools" . . some may asy why... the answer is that these "Advanced Tools" are the most useful ones i have found in my travels while creating this kitchen, I have not written about each one in the "How To Cook.pdf" but i may in the future. If you need help with these ask in the thread and i will update my first 2 posts accordingly.
.
.
Instructions
1) Download at least the following: Instructions, ROMDonalds Kitchen, Selection Of OEM Apps (Animated Startup Screens are just an extra if you want them!!)
2) Extract "ROMDonalds.rar" then RUN "ROMDonalds.exe"
3) Extract "Selection Of OEM Apps"
4) READ INSTRUCTIONS SLOWLY AND CAREFULLY
5) Enjoy
.
.
Download Links
Instruction Manual:
Sendspace - Last Updated : 29/07/07
Megaupload - Last Updated : 29/07/07
Rapidshare - Last Updated : 29/07/07
ROMDonalds Kitchen :
Whats Been Updated? - Advanced Tools Section Updated, initFlashFile Generator FIXED
Sendspace - Last Updated : 01/08/07
Megaupload - Last Updated : 01/08/07
Rapidshare - Last Updated : 01/08/07
Animated Startup Screens :
Sendspace - Last Updated : 28/07/07
Megaupload - Last Updated : 28/07/07
Rapidshare - Last Updated : 28/07/07
Selection Of OEM Apps :
Sendspace - Last Updated : 28/07/07
Megaupload - Last Updated : 28/07/07
Rapidshare - Last Updated : 28/07/07
Other Useful Links :
Available Radio ROMs : Click Here
2.10.Olipro (HardSPL v7) : Click Here
Hermes Upgrade Guide (mrvanx) : Click Here
Hermes Wiki : Click Here
Google Search Forums : Click Here
.
.
Attached Files
Notepad 2.zip This is a better text editor then notepad!
FOR BATTERY ICONS CHECK THIS THREAD
NEW THEMES PACK
NEW PACKAGE CREATOR:
Instructions
1: run the package creator
2: select open CAB and direct it at your CAB
3: When Cab Analyzer comes up, select extract (the icon 3 to the left of the folder icon with "MSCE" undernearth it) THis will open up the "extract" windows, you will notice that it is already pointing at a folder in your C:\XXXXX (XXXX will be the name of the CAB) you MUST extract it to this directory (it is only a temp and it will be moved to desktop in abit)
4: once extracted close the CAB manager, then the initflashfiles tab will open in the package creator. Select "enable options" then select your CUSTOM shortcuts (the initflashfiles.txt will already have the intended shortcuts in it, these are extra ones if you want any) when you have finished here press apply and done
5: set name for the option.xml and the section you want it to show in, then press complete package. On your desktop now you will find your package!
hope you like it, it is really fast once you get used to it!!
.
.
First to say you thank you. I was waiting for this. Great work Man.
hi - I like the name , i too believe in alot of manual cooking because i feel its the best way to learn. I use most of your tools and also htc rom tool by dark simpson. I'll have a look at your animated startup screens - been looking for those.
well done mate you deserved it. although i busy with my new toy in my sig I will give your kitchen a try to see what i can dish up for myself.
duttythroy said:
well done mate you deserved it. although i busy with my new toy in my sig I will give your kitchen a try to see what i can dish up for myself.
Click to expand...
Click to collapse
You will find the kitchen very familiar, it has nothing you wont have used already!! (although you may want to look at the advanced tools folder!!)
i would really appreciate it if you could cook and follow my instructions just to see in there are any obvious mistakes (Other than spelling & grammar!!)
Thanks alot
Great work man... will give it a spin later. Thanks
Nice work mate
Cooking for the masses eh, do you have a "drive through"
benec,
The combined clean battery and 3G icon cab does not work. I get a message saying that i dont have permissions to install that cab.
Trying to overrite the dll file into window also has the same effect
etreby71 said:
benec,
The combined clean battery and 3G icon cab does not work. I get a message saying that i dont have permissions to install that cab.
Trying to overrite the dll file into window also has the same effect
Click to expand...
Click to collapse
ok, i hadnt tested that, sorry about that, ill see if it can be fixed!!
The pdf says to run the powertoys program that is in the ROM tools folder, where is the rom tools folder?
sprice82 said:
The pdf says to run the powertoys program that is in the ROM tools folder, where is the rom tools folder?
Click to expand...
Click to collapse
appologies: it should read:
XP [FONT="]users run “CmdHerePowertoySetup - XP.exe” this is found in the “ROMDonalds” folder.
Instructions Download Links Updated 29/07/07 [/FONT]
This is great, easy to digest information, great work piecing all this together and writing the pdf.
One thing I must say is I very much do enjoy the use of the visual package selection method, manualley cooking in the cabs is great but being able to check a box next to what I want is always a plus.
twist said:
This is great, easy to digest information, great work piecing all this together and writing the pdf.
One thing I must say is I very much do enjoy the use of the visual package selection method, manualley cooking in the cabs is great but being able to check a box next to what I want is always a plus.
Click to expand...
Click to collapse
I like GUI cooking too, please dnt think i am belitteling other Kitchen designers!
MY problem's with the GUI cooking method are:
1) YOU DONT LEARN ANYTHING - THE MOST IMPORTANT PART - THE IDEA OF THIS KITCHEN IS TO TEACH PEOPLE WHAT GOES ON WHEN COOKING
2) its lazy, as the install screen of ROMDonalds says "Getting Something Is Good, Doing It Yourself Is Better!!!" (im not saying its not a great idea that people can customise their own ROMs that fast, and have whatever they want included)
3) its hard to modify an already cooked rom (i.e. Black Satin on Pandora)
4) its not guaranteed to work, stupid errors thrown up with no option to fix
5) if you cant change the base ROM you are stuck with it, also what you think is a good base, someone else may say sucks and visa versa
6) there is way more OEM software about than CAB's so if you manually cook, you are not restricted by what is included int he kitchen
I created a kitchen like this so i could learn in the way I WANTED to learn, not with some of the hap-hazard instructions there are available.
I found that through using the instructions i have published i have learned alot about the stages of cooking, so now, when i look at other kitchens, and it tells me to "Dump Rom" or "extract XIP" etc, i know wats going on!!
(also when errors in the GUI kitchens come up, i have a MUCH better understanding of where and why the error has occured!!)
I hope people find it as usefull as i have!
I love this kitchen I have allready learned TONS from it, I am just saying it would be nice to be able to use this kitchen AND be able to use a GUI for adding more packages as well.
But I completly understand your thinking and I definently have allready learned alot!!!
And again I appreciate your taking the time to put this together with a great PDF walkthru.
I am also wondering if there is anyway to delete something from the windows dir after it has been copied elsewhere ? or if you can move files instead of copying them. I am looking to cooking in Opera and it requires a few files in a few diffrent dirs and I would hate to have copies of these files in the windows dir and the dirs they are suppost to be in.
twist said:
I love this kitchen I have allready learned TONS from it, I am just saying it would be nice to be able to use this kitchen AND be able to use a GUI for adding more packages as well.
But I completly understand your thinking and I definently have allready learned alot!!!
And again I appreciate your taking the time to put this together with a great PDF walkthru.
I am also wondering if there is anyway to delete something from the windows dir after it has been copied elsewhere ? or if you can move files instead of copying them. I am looking to cooking in Opera and it requires a few files in a few diffrent dirs and I would hate to have copies of these files in the windows dir and the dirs they are suppost to be in.
Click to expand...
Click to collapse
you mean to create 1 folder called "Opera" and have all of the dir's and files for Opera inside that folder so you can drop it into the windows dir on a dumped ROM?
this can be done altho im not sure how, i want to include this into my instructions but as i said im not sure on how to go about it, JJ did it with some of the black ROMs, Satin definately.
only thing i can suggest is to dump SATIN and see how JJ did it!!
If you find anything please post it here so i can include it, and ill do the same.
Unable to find default.hv & user.hv in dump folder and a couple other questions
Hello Bennec83,
Thanks for the informative kitchen tools!! I am hoping to create a custom made ROM from these tools.
Question:
I have dumped the recently released Dopod ROM without difficulty and am now at the stage (stage C before C.1) of finding the two files in the dump folder: default.hv and user.hv ...I performed a search and then manually looked for the files without success. I have followed the format for dumping and I may be missing something but these files are not appearing...Any suggestions??
Also, if I wanted to delete say windows auto update or other folders in this ROM without creating a conflict, this dumping section would be the appropriate area, correct?? I guess this is the part where trial and error occurs...correct? I am trying to maximize storage space without conflicts.
Thanks so much for your time,
vjgrace
bennec83
GREAT work m8! Just read your cooking instructions and they are superb. I haven't tried the kitchen yet, but from what I read it is pretty straight forward and very well explained !
Thanks for creating this, I will test in the following days and let you know of my experience
Again, great work and keep us posted of any changes...
Twist in regards to cooking in opera - there is no way to delete the files after they are copied out of the rom. I know it seems wasteful but that is the way it is. Most cooks hence keep the inclusion of this type of app down to a minimum because of storage space. Would recommend compression of opera.exe to use less storage memory - and find the oem package so you can use the rgu and initflashfiles.txt from there to make life easier.
vjgrace said:
Hello Bennec83,
Thanks for the informative kitchen tools!! I am hoping to create a custom made ROM from these tools.
Question:
I have dumped the recently released Dopod ROM without difficulty and am now at the stage (stage C before C.1) of finding the two files in the dump folder: default.hv and user.hv ...I performed a search and then manually looked for the files without success. I have followed the format for dumping and I may be missing something but these files are not appearing...Any suggestions??
Also, if I wanted to delete say windows auto update or other folders in this ROM without creating a conflict, this dumping section would be the appropriate area, correct?? I guess this is the part where trial and error occurs...correct? I am trying to maximize storage space without conflicts.
Thanks so much for your time,
vjgrace
Click to expand...
Click to collapse
HI,
default.hv and user.hv are a pain in the arse to find, you need to change the folder options so you can "show hidden files and folders" AND uncheck "hide protected operating system files" (see screenshot)
then the next thing i do is order everything by type, then scroll down to "HV File" and you will find them both
with regards to your second question, this is about dumping and cooking a ROM.
a ROM is originally compiled from an operating system, to change features inside the OS you need to dump the ROM differently as this kitchen (at the moment) is only for adding and removing APPs and tweaks.
To do what you want you need to get the "SYS" "OEM" and "XIP" folders from your ROM, swap them into a different kitchen (one that allows you to run something called "BuildOS.exe" )
I will be releasing one here, but the first thing to do before you start messing with the OS of your phone, is to get used to doing the methods in this kitchen.
It is my Birthday today, so i cannot put together a "BuildOS" package and instructions today but I will, soon!!
hope this helps
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
As is.
Just press the "!COOK.CMD" file. (or make your changes before)
Old opinion:
>>8M of PP - after long time of testing looks as the optimal size for performance/RAM.<<
New opinion:
12M PP looks bit more responsible to interface.
New packages & drivers.
Tweaked several packages - for less memory use.
Tried to put all possible configs in one OEM/xxxconfig folder.
UC ready, - look to _ADDS/Internal Storage forder for example.
Mark all content of "Install" forder as "read only". Or you loose it after install or hard reset.
The best way - look inside "provision.zip" and make your own config file. Put it in "Install" folder and line as
"XML: \Storage\Install\provider.xml" to "sdconfig.txt".
Password for provision.zip you can find at the help page of Connection setup.
You need unsigned HardSPL!
Don't forget about hard reset after first install & make content of "Internal Storage/Install" READ ONLY!
RESOURCES
"LEGO": http://rapidshare.com/users/JW7QII
Snapshots: http://rapidshare.com/users/7L0TM7
Cabs: http://rapidshare.com/users/E8A83X
-=NEWS=----------------------------------
[2009.01.05]
MSXIP21109 & SYS21109(XIP inside) added to "Lego" repository.
-=NEWS=----------------------------------
------Check the time of upload, new version could be there: not the all changes going to the "NEWS" category -------
P.S. Remark for all:
I open this thread for people, who want to make own rom, but don't want spent the time for brutal operations.
Not all components is "mondi's original", - big thanks for
bepe,
swtos,
Niki,
Vic5870,
AVLev,
Prewien,
lexxirae,
and others for ideas and work.
It's only "timepoints" of my kitchen. With bugs, mistakes etc.
Will be glad to see opinions, founded bugs, new ideas.
EVERYBODY CAN USE IT AT ALL, if they use it for private ROM or follow the same "open" politics.
i get errors when extracting. winzip says its corrupt and win rar says invalid or corrupt authenticity information. win rar will complete the extration, but i'm not about to flash anything when there are errors. maybe upload again?
MD5:
18ebc1fbaaca73df8ff6124ad4296db3 *1.97.20755_Diamond.rar
19befa01daf491d6c838fa8d38d8096a *KITCHEN_20755_WWE.RAR
2bdceea4e5642f9f4066ed858041c086 *1.97.20755.nbh
Check it.
I'm downloading back now. Will see.
Used winrar 3.80
..............
1.97.20755_Diamond.rar has checked: passed
1.97.20755.nbh has checked: passed
KITCHEN_20755_WWE.RAR has checked: passed
Thanks man,
going to try it now
If I can do anything, just let me know...
hi,
at first, i have the same problem with extracting (3.8) and authentification,
but it extracts ... i dont know, if some files wouldnt extract?
the second is
"AAAAAAAAAAAAAAAAAAAAAAARGH" !
where you are the last weeks during i flashing my rom with kaiserkitchen
(it's very good, but for beginners its very strong ... with a liitle time spend
and reading here and reading there its gone) ?
i cooked my own rom ... i think its 3 houers before ...
its always the same - iam finishing with this one - than an other cooker/flasher puts a new thread and all the works begin at zero.
but that is it what we love i think.
i will use my rom for 3 or 4 houers than i will test/use your kitchen
thank you for your work.
okokur
p.s.
my english is not so good and the time its gone to morning,
my comment to your thread means positiv/happy. it dont means any angries
Hello!
I repeat: it's not "my" kitchen.
"My" is only changes in OEM/SYS/ROM folders.
I like this kind of kitchen for useful "stepping".
Forgot, where did I find it. Somewhere here
Bit later will be update to 20757 (HD ported).
This kitchen seems of no use to me.
It needs .nb, .wrn and other files which are'n present.
Maybe some explanating how to get them, I would like to try it.
pietrucci said:
This kitchen seems of no use to me.
It needs .nb, .wrn and other files which are'n present.
Maybe some explanating how to get them, I would like to try it.
Click to expand...
Click to collapse
???
Just press !COOK.CMD.
May be damaged archive? Check the md5 sum to arh.
Ok, sorry it's working now...
Another question: a lot of files are from date 10th of July, for example the manila files. Does this mean these files really are so old???
The latest versions of manila are of a newer date are they?
pietrucci said:
Ok, sorry it's working now...
Another question: a lot of files are from date 10th of July, for example the manila files. Does this mean these files really are so old???
The latest versions of manila are of a newer date are they?
Click to expand...
Click to collapse
Marked "stable" original Diamond manila.
If you want the alternative - look to the "_OUT" folder.
Updated to Blackstone's XIP/SYS 20757.
Manila updated to last "official": 1.1.35097.1_1630.38
Style to gray.
I just got my Diamond 2 weeks ago. I cook my first ROM using your kitchen tree but I have some questions:
1. Why the setting up screen is all black ? I thought there were some sort of Windows Mobile 6 background
2. I tried to set up bluetooth but it shows me a message box with something like "No bluetooth hardware"
I follow the instructions by just clicking !Cook.cmd. I didn't change anything in your packages. Did I do something wrong ?
Please advice. By the way, thanks for this kitchen tree.
dafeke said:
1. Why the setting up screen is all black ? I thought there were some sort of Windows Mobile 6 background
Click to expand...
Click to collapse
It's just my choice: less using rom/ram memory. And not important at all. You can use yours pictures. It is the kitchen, isn't it?
dafeke said:
2. I tried to set up bluetooth but it shows me a message box with something like "No bluetooth hardware"
I follow the instructions by just clicking !Cook.cmd. I didn't change anything in your packages. Did I do something wrong ?
Click to expand...
Click to collapse
I'll see. I use BT very seldom. Didn't check it, just put the packages.
mondilv said:
It's just my choice: less using rom/ram memory. And not important at all. You can use yours pictures. It is the kitchen, isn't it?
I'll see. I use BT very seldom. Didn't check it, just put the packages.
Click to expand...
Click to collapse
I coocked my ROM with version 20755: everything's fine here with bluetooth (and all other stuff). I use bluetooth for my carkit, works fine.
I benchmarked this ROM with my usual benchmarks: it's pretty fast compared to others! I left out Opera and Google Maps, but I don't think that makes a big difference in benchmark results.
I will try your Blackstone upgrade this evening, I'm curious if that's faster than the 20755... (in fact I don;t think so).
There is one strange thing in this one: I can't change pagepool. Using pagepoolchanger.exe it says it can't find the right address...
Keep you informed...
Thank you mondilv for the this kitchens! Great job
pietrucci said:
I coocked my ROM with version 20755: everything's fine here with bluetooth (and all other stuff). I use bluetooth for my carkit, works fine.
I benchmarked this ROM with my usual benchmarks: it's pretty fast compared to others! I left out Opera and Google Maps, but I don't think that makes a big difference in benchmark results.
I will try your Blackstone upgrade this evening, I'm curious if that's faster than the 20755... (in fact I don;t think so).
Click to expand...
Click to collapse
Agree. I did benchmarks too. (?)
BT fix - in the first post (from 20755 SYS). Works now.
pietrucci said:
There is one strange thing in this one: I can't change pagepool. Using pagepoolchanger.exe it says it can't find the right address....
Click to expand...
Click to collapse
pagepoolchanger.exe don't works to Diamond (use search - don't remember, where is the info). Use hex editor.
...and NB container is reduced by uldr, - only one needed address.
pietrucci said:
Keep you informed...
Click to expand...
Click to collapse
Thanks for cooperation!
mondilv said:
Agree. I did benchmarks too. (?)
Click to expand...
Click to collapse
I suppose you use the ? because you don't know why I make this remark? Well, if you like take a look at my thread: http://forum.xda-developers.com/showthread.php?t=406640, you can compare this ROM with many others, all tested on the same device, under the same circumstances, more or less.. I will add this ROM's benchmark results later this evening.
mondilv said:
pagepoolchanger.exe don't works to Diamond (use search - don't remember, where is the info). Use hex editor.
...and NB container is reduced by uldr, - only one needed address.
Click to expand...
Click to collapse
PagePoolChanger DOES work on most 'normal' Diamond ROMs, I've used it many times before. But I guess it conflicts with the uldr thing... no problem.
here friend... like mentioned in a PM sent you this morning... I'm porting some pieces of your base sys/xip for including in my rom (dia duit), of course I'll mention that the base rom comes from your hard work
instead of upgrading the whole sys I prefer to choose faster/smaller dlls between different sys
anyway also my rom is open, because I strongly believe that this is the only way to proceed to a faster development... by sharing infos each other
but I'll prefer to share the whole kitchen on my 1st stable release, now we are at v08, because till now my rom has some bugs
thx mate!
bye,
davide
pietrucci said:
I suppose you use the ? because you don't know why I make this remark? Well, if you like take a look at my thread: http://forum.xda-developers.com/showthread.php?t=406640, you can compare this ROM with many others, all tested on the same device, under the same circumstances, more or less.. I will add this ROM's benchmark results later this evening.
PagePoolChanger DOES work on most 'normal' Diamond ROMs, I've used it many times before. But I guess it conflicts with the uldr thing... no problem.
Click to expand...
Click to collapse
here how to change PP on diamonds:
open final .nbh file with a hex editor (I use pspad)
search the following hex value: 389FE550089FE5
as you find it change next two numbers (in an original rom, these two values are 00 25)
search again for the same hex value, again you need to modify the adjacent two values (in case of an original rom, these two values are 03 25)
values:
for pp 0 Mb: 00 25
for pp 8 Mb: 02 25
for pp 12 Mb: 0C 26
for pp 16 Mb: 10 26
of course I wasn't able to find alone... I found thx to the great & nice Seatone
have fun
pietrucci said:
I suppose you use the ? because you don't know why I make this remark?
Click to expand...
Click to collapse
I was bad surprised too. Quite big diff between close versions. About 5%, isn't it?
After trying several combination of xip/sys me like 20755 at last time.
Or xip757/sys755 - no bad too.
pietrucci said:
Well, if you like take a look at my thread: http://forum.xda-developers.com/showthread.php?t=406640, you can compare this ROM with many others, all tested on the same device, under the same circumstances, more or less..
Click to expand...
Click to collapse
I good know your thread
pietrucci said:
I will add this ROM's benchmark results later this evening.
Click to expand...
Click to collapse
Early, I think. Can't to call its rom stable. Just found more bugs, think not the last for today (lighting for missed call is absent; green element in manila)
I return to home now, so new version could be tonight.
pietrucci said:
PagePoolChanger DOES work on most 'normal' Diamond ROMs, I've used it many times before. But I guess it conflicts with the uldr thing... no problem.
Click to expand...
Click to collapse
May we use different versions?
"My" looks properly worked, but by devhelth.exe - PP didn't changed.
SuperJustKitchen v0.9 Released.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices, eventually.
Word of warning:
Not all EXT's have been tested or modified for the every device. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.) Some packages will only be compatible with some devices.
(I'm no longer updating each thread separately for each device but just updating my site and posting the release info here. I will only update each thread to say that a new version is out.)
**Warning**
Before using this kitchen, you MUST read the whole thread. Any questions that have been answered will be ignored. This is your only warning.
**Disclaimer**
I am not responsible for any damage that may be done to your phone with a ROM created in this kitchen.
I am not responsible for any damage done to your computer.
I am not responsible for anything... at all.
Introducing SuperJustKitchen!
SuperJustKitchen is based on [http://forum.xda-developers.com/member.php?u=843218"]airxtreme[/URL]'s osKitchen Zero. All credit on for the kitchen backend goes to him.
Features
A completely stripped ROM. (Work in progress for some devices.)
LZX and XPR compression (Also option for No compression.)
Auto clean files that are language specific or DPI specific that your ROM does not need
Auto port missing language MUI files
Automatic rec'loc'ing for devices without native 6.5 nk's
6.1 and 6.5 support
Auto XIP and SYS porting
Auto NBH packing
Tool to convert OEM packages to EXT packages
Auto file conflict fix (don't have to removing older file that conflict (not that there are any. )
Save custom ROM settings (for cooks for multiple ROMs)
Cook multiple languages at the same time with the same ROM settings (Have to add language support yourself. I removed the required MUI's a while back because they made updating the kitchen and adding devices a nightmare.)
MUCH better organization of EXT packages
Active development instead of a program that is no longer being developed
Cleaner and easier to use interface
A built-in and customizable Tutorial section
And more!
Builds included
21056 - WM6.1
23658 - WM6.5 with new redesigned GUI
At the moment, this is an ENGLISH (WWE) only kitchen. This might change...
NOTE: In order for me to keep track of whether my time was well spent or wasted, if you use this kitchen to make a ROM, please either include SJK in the name or just mention that it was SJK cooked in your ROM's thread.
NOTE: This kitchen assumes that you know how to flash through SD, recover from a bad flash and are able to backtrack your steps to figure out how you broke your own ROM. If you do not understand these, please learn them first. Do not PM me asking me. I have written numerous walkthroughs on all these except on how to backtrack your steps. For that, just remember what you're doing as you do it and keep backups.
If you find any issues, PLEASE report them to the bug tracker in my website. It will help me make this kitchen better!
ENJOY!!!
Well ... I have repaired my Hermes yesterday and now I'm trying ROMs here and none of them really suits me.
So your SJK came in the right time. I did few ROMs for myself last year, so I'm gonna try your SJK probably this evening.
And if it will work flawlessy, I'm considering donation.
Impressive..
Downloading and will hopefully be trying this out soon.
Let me know if you run into any problems with the native nk and changing the pagepool. (I don't have a test device, unfortunately.)
ivanmmj said:
Let me know if you run into any problems with the native nk and changing the pagepool. (I don't have a test device, unfortunately.)
Click to expand...
Click to collapse
I am cooking a 23529 native build now and will know here soon
Well, I have built 6.5.x ROM with native kernel and 16MB pagepool. I didn't add anything in the ROM and I'm missing Camera, CommManager, ClearStorage and stuff like this in the ROM. Suppose I have to add them externally.
Now I'm gonna try adding some things and changing pagepool etc.
pajousek said:
Well, I have built 6.5.x ROM with native kernel and 16MB pagepool. I didn't add anything in the ROM and I'm missing Camera, CommManager, ClearStorage and stuff like this in the ROM. Suppose I have to add them externally.
Now I'm gonna try adding some things and changing pagepool etc.
Click to expand...
Click to collapse
You have to actually add them in the EXT packages. They are not built in so that you can choose your own. I stripped the OEM and created packages of all required programs and made them into EXT packages.
Ooops, my bad. I've just extracted EXT, SYS, SJK, HERMES archives and didn't check the wrong paths. Because everything puts itself in Sources and the EXT has got Working_Folder/EXT instead of Sources/EXT.
I was wondering why I can't see any EXT things in the osKichten.exe
I must be doing something wrong then cause mine won't go past the boot screen using native. I used everything default. Will try again.
This has happened to me the first time i tried this Kitchen ... then I've tried it again and it worked.
But I'm havning problem with the EXT. I can't select packages from the folders. I can just select folders. :\
EDIT: Ok, I surreder - where are the C_cingular, C_xyz.cab things? I can't find them anywhere to get rid of them.
pajousek said:
Ooops, my bad. I've just extracted EXT, SYS, SJK, HERMES archives and didn't check the wrong paths. Because everything puts itself in Sources and the EXT has got Working_Folder/EXT instead of Sources/EXT.
I was wondering why I can't see any EXT things in the osKichten.exe
Click to expand...
Click to collapse
You have have accidently downloaded v0.7 of the EXT which is a COMPLETELY different kitchen.
This has happened to me the first time i tried this Kitchen ... then I've tried it again and it worked.
But I'm havning problem with the EXT. I can't select packages from the folders. I can just select folders. :\
EDIT: Ok, I surreder - where are the C_cingular, C_xyz.cab things? I can't find them anywhere to get rid of them.
Click to expand...
Click to collapse
I'm not sure what you mean. Can you please post a screenshot?
ivanmmj said:
You have have accidently downloaded v0.7 of the EXT which is a COMPLETELY different kitchen.
I'm not sure what you mean. Can you please post a screenshot?
Click to expand...
Click to collapse
Well, the first issue (not showing apps) was cause by the 0.7 version instead of 0.8 ... i really should give more attention to what I'm downloading.
The EDIT line, about C_Cingular_GoodEmail*.cab, PT_Cingular_Whitelist* etc. - those are apps which are automatically installed after first boot. I suppose it's cause by the line "EXEC:\Extended_ROM\autorun.exe" in PreConfig.txt in OEMOPERATORS. But - where does that autorun.exe has it's config? and where's Extended_ROM in the Kitchen? Because afaik it isn't the same as EXT?
EDIT: I got an idea - aren't those cabs just remains of the ExtROM from AT&T ROM? Then, howto delete them? By making my ROM BigStorage? :|
pajousek said:
Well, the first issue (not showing apps) was cause by the 0.7 version instead of 0.8 ... i really should give more attention to what I'm downloading.
The EDIT line, about C_Cingular_GoodEmail*.cab, PT_Cingular_Whitelist* etc. - those are apps which are automatically installed after first boot. I suppose it's cause by the line "EXEC:\Extended_ROM\autorun.exe" in PreConfig.txt in OEMOPERATORS. But - where does that autorun.exe has it's config? and where's Extended_ROM in the Kitchen? Because afaik it isn't the same as EXT?
EDIT: I got an idea - aren't those cabs just remains of the ExtROM from AT&T ROM? Then, howto delete them? By making my ROM BigStorage? :|
Click to expand...
Click to collapse
Fixed for next build. ^_^
For now, just remove the preconfig.txt file.
Please report any future bugs to the bug tracker. (There are way too many threads to keep track of all of them.)
I've registered to bugtracker ... and the confirmation email didn't come, so I can't post new bugs. I guess I have to post it as guest?
pajousek said:
I've registered to bugtracker ... and the confirmation email didn't come, so I can't post new bugs. I guess I have to post it as guest?
Click to expand...
Click to collapse
I activated you manually. I'm not sure why it's not sending out the emails. I'll look at the code of the site.
I take it this isn't bigstorage? If not do you plan to have one bigstorage? I'd like to be able to do bigstorage in 6.1 and 6.5 and this looks like my best option..
thanks
Since the bugtracker is broken:
These things are buggy:
any Connection Wizard - I can't get it to work
Dialer - Every dialer is buggy and if I try to cook there else OEM Dialer (found by google), it doesn't work too
ClearStorage - doesn't do hardreset
Then I'd appreciate battery.dll which is by 1% and not 10%.
Making the ROM BigStorage would be a big plus too. And AFAIK I shouldn't have 39MB RAM with 6MB PagePool? 39MB is for 16MB PP, right?
MrDSL, are you experiencing anything of these issues too?
pajousek said:
Since the bugtracker is broken:
These things are buggy:
any Connection Wizard - I can't get it to work
Dialer - Every dialer is buggy and if I try to cook there else OEM Dialer (found by google), it doesn't work too
ClearStorage - doesn't do hardreset
Then I'd appreciate battery.dll which is by 1% and not 10%.
Making the ROM BigStorage would be a big plus too. And AFAIK I shouldn't have 39MB RAM with 6MB PagePool? 39MB is for 16MB PP, right?
MrDSL, are you experiencing anything of these issues too?
Click to expand...
Click to collapse
Strange. I'll have to test the connection wizards on the wing.
The dialers work fine on the wing. Does the dialer named Hermes work? (It's directly from the Hermes.)
ClearStorage - Your device might require an older clearstorage. I'll have to look for one.
That sounds like the native 6.5 nk isn't getting its pagepool changed.
I'll see about that. The Hermes 6.5 nk is notorious for most pagepool tools not working on it.
As far as the bigstorage. Give me a link to it and I will see about including it.
well, i'll try the not-native kernel (what disadvantages it has anyways?)
about bigstorage & clearstorage & dialer - i'll do some searching and testing and send you working links (since you don't have testing device).
ivanmmj said:
Strange. I'll have to test the connection wizards on the wing.
The dialers work fine on the wing. Does the dialer named Hermes work? (It's directly from the Hermes.)
ClearStorage - Your device might require an older clearstorage. I'll have to look for one.
That sounds like the native 6.5 nk isn't getting its pagepool changed.
I'll see about that. The Hermes 6.5 nk is notorious for most pagepool tools not working on it.
As far as the bigstorage. Give me a link to it and I will see about including it.
Click to expand...
Click to collapse
I have yet to get a ROM past the boot screen So I dunno..
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