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
I have searched for the last 2 hours and cannot come up with a good answer.
I have a collection of various ROMS that people have cooked up, for instance Blinky and others. There are some items I would like to grab from these ROM sets and either make my own or install a ROM and install these other file individually from the .cab files.
I guess the question is how would I go about tearing apart the .nbh file so I could get what I wanted from it?
ThanX in advance.
Use ROMDonalds kitchen to extract whatever you want out a ROM. Use the signature link before to search for the Kitchen!
Hi here i release an OLD style kitchen based on Bepes tools
I have taken bepe's kitchen and created some batch files to make it a one click extract and one click build and flash
I was so used to the old style kitchens and when they stoped working (failing at xip extract) i was looking for something that worked that i could use easly.
I found bepes kitchen, and it was nearly the same so i ported the batch files from diamond kitchen 0.4 to make this.
this kitchen uses the new style packages but has the look and feel of the diamond kitchen 0.4
I am still looking for the package creater that makes these NEW style packages but can't seem to find it now so if anyone has it please drop me a link so i can include it in the kitchen tools
download link ---->
http://rapidshare.com/files/217781904/Kitchen.rar
Instructions
1 place you RUU_Signed.nbh in the baserom folder
2 click on !Begin
3 Dont touch anything until extraction is finished (approx 5-10minutes)
4 Modify your packages
5 click on !Cook
6 wait until the htc rom tool loads
7 select diamond in device, os.new.nb as the source OS and save as kitchen/RUU_Signed.nbh
8 close htc rom tool and Custom RUU flash tool will load
9 flash and enjoy
......
will this kitchen group the OEM and SYS files properly. im having difficulty in using the new format or everything's in SYS\MSXIPKernel folder.
Is the Rom dump protected after cooking?
DefJamz said:
will this kitchen group the OEM and SYS files properly. im having difficulty in using the new format or everything's in SYS\MSXIPKernel folder.
Click to expand...
Click to collapse
this dumps the rom into the OEM, SYS and ROM Folders if you want the EXT folder download Bepe's tool below OEM2EXT
RideTheTube said:
Is the Rom dump protected after cooking?
Click to expand...
Click to collapse
not had time yet to try and test if i can rebuild a cooked rom, will have a go tonight and post my findings.
This is Bepe's Kitchen automated by batch files so he is the best person to talk to about protection
sorry to be a little blunt but i am a noob when it comes to cooking that why i found something that worked for me and made it a little easyer to use,
Protected Rom? Almost Rom when rebuilding, it will delete all dsm file, so you can't use package tool.
ok i have now tried the flashing, and the cooked roms won't pass the splash screen page, not getting the device info in bottom right corner.
anybody there who uses bepe's kitchen mind having a look for me.
also i can't open a re-cooked rom
garymeg said:
ok i have now tried the flashing, and the cooked roms won't pass the splash screen page, not getting the device info in bottom right corner.
anybody there who uses bepe's kitchen mind having a look for me.
also i can't open a re-cooked rom
Click to expand...
Click to collapse
I had the same problem and it was a XIP "mess-up". however I can't help you more than this.
try asking here: http://forum.xda-developers.com/showpost.php?p=3575850&postcount=131
i simply do NOT understand why build a tool that deletes stuffs that are important for cooking. isnt rom cooking supposed to be an open project for ALL? i mean some chef have the donate button in their sigs. but their rom's locked. it isnt fair to those (like myself) trying to learn how to cook a rom. i mean, i try to compare official roms and custom roms insides. what are the difference. it's by comparing that people learn to differenciate. and i would say BAHHH to missing rgu and dsm files!!
My thoughts exactly... Alas...
it is ironic, that NONE of the chefs who lock roms/doesn't supply kitchen/ask for donation wrote the code themselves. In short - everybody operates on stolen/leaked or any other way obtained code.
Ok, there are authors who created tools. And those guys have full right (and reason) to ask for donations fro that - TOOLS.
Otherwise - it's just funny. it's like stealing a car, and then asking police to protect it....
no panic.
at normaly old style kitchens never delete dsm'S.
and if you delete manualy dsm'S, you get all files in folder.
i think, with protect rom it means, no recookable roms.
it stops at point 1 or in the first step by using BEGIN! with a message like
"rom is smaller/bigger than/at starts" or so. excuise me, i've forgot the exactly words.
for checking of recookable rom i checked it with "htcRIE_0.5.0.12.exe".
it shows you all files with oem/sys - folders. but the oem can be empty. you find the oem-files than in sys-folder.
these points are my thinks that i see/learned by beginning flashing and cooking until now. other people can see/learn other thinks so dont dismiss me, if you are not my oppinien - but you can dismiss my english
Htc rom tool
Is it possible to use this for the Fuze?
EDIT: I found HTC tools with support for more phones on this thread a couple posts down
Well, I've seen many chefs who use this tool to install various programs. How can I utilize this tool? I have searched all over to no avail
I'm assuming you mean the User Configuration (UC) feature. If not, then I apologise. I did a search and found an old thread explaining it here.
steviewevie said:
I'm assuming you mean the User Configuration (UC) feature. If not, then I apologise. I did a search and found an old thread explaining it here.
Click to expand...
Click to collapse
Nah thats not it, but thanks for trying =P
What i'm looking for is how to use the customization tool that comes up after flashing a rom. In several roms after the first boot it will say Wait a few minutes for customization to complete or something like that. I'm looking for a tut explaining how to use this tool to cook certain programs into my rom without converting them into ext, Thanks for your help though Stevie.
ok, I thought that was it, UC can be used to run cabs and stuff. But sorry for my misunderstanding, hope you find it soon !
husker91 said:
Nah thats not it, but thanks for trying =P
What i'm looking for is how to use the customization tool that comes up after flashing a rom. In several roms after the first boot it will say Wait a few minutes for customization to complete or something like that. I'm looking for a tut explaining how to use this tool to cook certain programs into my rom without converting them into ext, Thanks for your help though Stevie.
Click to expand...
Click to collapse
I'm not sure about your kitchen, but when I used the JoshKoss/TwoPumpChump Kaiser kitchen to cook ROMs, you would place all the applications in a special folder and create a text file called config.txt in that special folder pointing to the location of all your .cabs. You would then cook the ROM, and all the .cabs in that folder would end up in \Windows on the device after a flash. On first boot, it would install all of the .cabs you'd referenced in that file.
I would check in your kitchen's thread, as there will probably be questions from people like you. Try searching for config_operator.txt, config_PT.txt, or config_AP.txt in that kitchen's thread. Alternatively, you could very politely PM a ROM cooking veteran like NRGZ28 or joshkoss (or another chef) and ask how to do this. Sorry I couldn't be more specific to your, but hopefully that'll point you in the right direction.
DaveTheTytnIIGuy said:
I'm not sure about your kitchen, but when I used the JoshKoss/TwoPumpChump Kaiser kitchen to cook ROMs, you would place all the applications in a special folder and create a text file called config.txt in that special folder pointing to the location of all your .cabs. You would then cook the ROM, and all the .cabs in that folder would end up in \Windows on the device after a flash. On first boot, it would install all of the .cabs you'd referenced in that file.
I would check in your kitchen's thread, as there will probably be questions from people like you. Try searching for config_operator.txt, config_PT.txt, or config_AP.txt in that kitchen's thread. Alternatively, you could very politely PM a ROM cooking veteran like NRGZ28 or joshkoss (or another chef) and ask how to do this. Sorry I couldn't be more specific to your, but hopefully that'll point you in the right direction.
Click to expand...
Click to collapse
exactly what I needed to know, Thank you very much. I'm using ervius visual kitchen but the config.txt and such work in a similar manner. Thanks again
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