Related
Hi all,
I've managed to find a dump of build 19900, however I haven't managed to make a working ROM out of it as yet. I'm hoping to find a way to get it working with bepe's kitchen tools - therefore removing the reliance on a custom chinese binary to build these ROMs.
I believe this ROM is big storage, so I'd like to make available a non big storage version as well for everyone to benefit.
Any takers to help out?
Download URL: http://rapidshare.com/files/113432995/Hermes_RomKitchen_19900.rar
CRCinAU said:
Hi all,
I've managed to find a dump of build 19900, however I haven't managed to make a working ROM out of it as yet. I'm hoping to find a way to get it working with bepe's kitchen tools - therefore removing the reliance on a custom chinese binary to build these ROMs.
I believe this ROM is big storage, so I'd like to make available a non big storage version as well for everyone to benefit.
Any takers to help out?
Download URL: http://rapidshare.com/files/113432995/Hermes_RomKitchen_19900.rar
Click to expand...
Click to collapse
Will take a look at it dude, aint got a load of time at the mo though. Might have a quick PM session and see if theres a WWE version we cna use.
Have you guys tried PM'ing Dvha79_ddt? I'm not much help on cooking but i'll try and suggest anything
Good luck guys.
Need testers let me know.
I've managed to get the ROM to build using Bepes kitchen, however it doesn't boot. It sits there at a black screen on power on...
This leads me to believe it's part of the XIP that is just wrong.
I've attached what I've extracted from the included os.nb by doing:
nbsplit -hermes os.nb
RomMaster -w 5 os.nb.payload -x -o xip.bin
Run xipport, choose Dump xip.bin
I then deleted os.nb & os.nb.extra.
Then put the XIP dump together as it should be (i think) for bepe's kitchens.
Not 100% sure where to go from here...
edit: Oh, I've attached the TOOLS directory too - just in case you don't have a copy of Bepes great work.
This is a non big storage modded 19900 xip that works.
I haven't used in a kitchen just yet.
I will have a look at the dump later on.
dan1967 said:
This is a non big storage modded 19900 xip that works.
I haven't used in a kitchen just yet.
I will have a look at the dump later on.
Click to expand...
Click to collapse
Hmmm - I've used your XIP - it boots, but same as using the default ROM kitchen tools, it hangs after displaying splash2. I replaced the OEM_FLASHDRV.DLL in OEMDrivers with a non-BS version, in case that was an issue, but still no go...
CRCinAU said:
Hmmm - I've used your XIP - it boots, but same as using the default ROM kitchen tools, it hangs after displaying splash2. I replaced the OEM_FLASHDRV.DLL in OEMDrivers with a non-BS version, in case that was an issue, but still no go...
Click to expand...
Click to collapse
For now you can try to merge that XIP with the payload from the ROM (without kitchen) and it should boot&work.
Will try to get the romhdr.bin and in fact to rebuild the whole ROM folder and let u know whats happening.
Using Dvha79_ddt 900
I know it's not what you are looking for, but I am using Dvha79_ddt ROM and it is working as well as his 701 which was very fast and rock solid. Would like to help in any way I can as I loved your ROM's apart from the issues. As a noobie where do you find these ROM's in the first place?
A lot of it is hit and miss finding things here and there - like this kitchen that seems to be almost complete, but just doesn't work. A bit of hacking around and it can probably be made to work.
As WM6.1 doesn't exist for the hermes devices, it is always ported from something else - which can lead to weirdness.
Most of it is pot luck, and a lot of knowledge (and I'm missing some in getting this kitchen working )
just a working trick
what I am sure is working (tried it before) is replace the whole ROM folder from new kitchen with your working one and then just slip in the xip.bin into the new payload in a few steps.
Still can't get this working....
I've changed the BuildNB.bat to show the following:
Code:
echo.
CD ROM
..\TOOLS\buildxip.exe -b
if not "%errorlevel%"=="0" goto error
del out.bin
copy xip_out.bin out.bin
CD..
This should use your XIP in the ROM, which shows as 3.62.07.Dan - however I still can't get past splash2... Eventually, the backlight goes out, but it doesn't seem to display anything past splash2... Eventually, the screen goes off (power setting). Turning it back on via the power button just gives me a white screen... I'm at a loss to figure out what's happening here.
The OS.nb.payload is the same (non-BS) that I was using from my 10.1 release of my ROM, and the XIP folder contains the same XIP as 10.1 release (Build 19209) - however the XIP version shouldn't matter, as we delete it and merge yours into the OS-new.nb instead...
About the same happened to me and after a re-flash of a good nbh I got some very strange things happening. I could not install any cab. Very weird.
I had to format everything.
Anyway the xip is working if slipped into old rom, but that's not much of a news...
I looked into S00 of FLASHDRV.DLL module in order to convert it, but it does not look like usually.
Maybe that dump is not from a hermes device.
Hrrrm - that is possible, however the site said that it was for Hermes devices... Are you looking at it in the OEMDrivers directory or the XIP?
Can we swap out the FLASHDRV.DLL from a working ROM? I'm pretty sure that isn't tied to a certain build?
CRCinAU said:
Hrrrm - that is possible, however the site said that it was for Hermes devices... Are you looking at it in the OEMDrivers directory or the XIP?
Can we swap out the FLASHDRV.DLL from a working ROM? I'm pretty sure that isn't tied to a certain build?
Click to expand...
Click to collapse
I can try to make it work with the XIP from the 19900 version existing on this thread. (actually from there was the xip I uploaded). Could it work? There will be maybe a 409 & 804 conflict?? I have no clue really. Can only try.
I don't believe the XIP is localised, nor are the OEMDrivers. I may be wrong here though. 409 vs 804 should in theory only become an issue when applications that use localisation is involved..
It is definitely not a hermes rom as the kitchen does not accept a hermes payload while other kitchens accept older (different) payloads. Kitchen halts at ImgfsFromNb.
I can not think of something else. I give up on this one.
Hrrrmmm...
What about this:
ftp://user:[email protected]:333/Aikon/Build19900RKXiaoQiao.7z
It weighs in at 145Mb, but it is supposed to be another Hermes 19900 kitchen that I haven't managed to get going either...
The XIP definatly isnt localised at all,
What sort of sizes are you guys getting for the os.nb filesize?
CRCinAU said:
Hrrrmmm...
What about this:
ftp://user:[email protected]:333/Aikon/Build19900RKXiaoQiao.7z
It weighs in at 145Mb, but it is supposed to be another Hermes 19900 kitchen that I haven't managed to get going either...
Click to expand...
Click to collapse
The download speed is obscene. It will finish maybe tomorrow.
I have been working on this new ROM Kitchen project over the last months.
Public beta can be found here:
http://www.darkforcesteam.com/showthread.php?p=3560
Downloading this minute. Is it also for old devices? (Blue Angel?)
Sounds great, thanks for this kitchen
motisu said:
Downloading this minute. Is it also for old devices? (Blue Angel?)
Click to expand...
Click to collapse
Should theoretically work for all HTC devices.
Only have an HTC Diamond to try it myself, but others tested it on Universal, HD, Raphael, ...
Nice to see you back Bepe!, Happy New Year
OMFG
bepe, you've completely outdone yourself this time!!! Checked out the videos, looks amazing!! Congratulations.
Downloaded, will check it out and post results. Thanks!!!
Hmm.it will work on all htc devices.
maybe some older dev cant use,need to test by yourself
really nice Rom Kitchen.
Great jod!!!
Cheers
Monkeybape
i second the post with the video tutorial !! great work and even me is able to build a rom now *lol*
Is removal of unneeded files from XIP supported, bepe??
this look fantastic bepe, as usual
even though I have tested it, I noticed two things:
1. Wouldn't replacing WINCE_NLS in the XIP from a different device, let's say, cause the phone not to boot?
2. What if the device you are porting from has a different resolution, wouldn't you have to change the files in the SYS manually?
other than that, it looks GREAT!
thanks again
chavonbravo said:
Is removal of unneeded files from XIP supported, bepe??
Click to expand...
Click to collapse
yes, it possible to add/remove all files/modules you want. It works the same way as in IMGFS... just delete the file/module from the XIP package or add a new one to an existing or new package.
the Kitchen will not include files that are not needed like boot.rgu, *.rgu, *.dsm to the XIP section, so there is no need to remove them after the XIP partition is build.
mbarvian said:
this look fantastic bepe, as usual
even though I have tested it, I noticed two things:
1. Wouldn't replacing WINCE_NLS in the XIP from a different device, let's say, cause the phone not to boot?
2. What if the device you are porting from has a different resolution, wouldn't you have to change the files in the SYS manually?
other than that, it looks GREAT!
thanks again
Click to expand...
Click to collapse
1. replacing WINCE_NLS is not really a problem, but the size of the .nls file might be.
example:
- you are using a WWE Kitchen with a WWE nls size: 267 KB
- you want to change lang to CHT, the nls size would be 1500 KB
--> this means the size of the xip section would grow very much
--> ROM\os.nb.payload is WWE and would not have enough space for the bigger CHT XIP
--> ImplantXIP.exe should give you an error I think... never tried it...
solution: use the CHT os.nb.payload (just replace the WWE .\ROM\os.nb.payload by the CHS one)
The CHS roms would have more space for XIP, so all would be working fine
2. Using another resolution is not a good idea... most SYS packages are compatible, but there are packages like this:
- Base_DPI_192 - this is for 192 DPI like Diamond, Raphael, HD
- Base_DPI_96 - only for QVGA devices
- base_dpi_192_resh_480_resv_640 - this package tells you the exact resolution it was made for
You could mix two builds, like using only new packages without *_DPI_192 or *_dpi_192_resh_480_resv_640 in the name...
... but not really a good idea, even that many ppl are making that. Consider that there might be resources that might be changed
Would take a look at it, but the forum requires compulsory registration to view.
Please fix your forum.
It tells me I'm missing msvcr71.dll when I try and dump. I noticed that file is other kitchens so I tried to copy it over and it starts the dump but then RecMod.exe stops responding and it asks to close.
I keep getting this error when it comes to running platformbuilder
Code:
This aplication has requested the runtime to terminate it in an unusal way
boo, I wanted to watch the tutorial on your forum again, getting an initflashfiles .dat not where it's supposed to be error. but your forum seems to be down, or under too high traphic right now, is there any way you would think of putting together a short text based info set on everything we need to know to dump and rebuild? if not, no biggie, I am sure I will figure it out, like any great new tool, there is always a learning curve Thanks much for sharing your work with all of us though
Good to see you back bepe!!! I will give this a shot later on today...
outstanding bepe!! I thought your tutorials were excellent too!
thanks bepe
tested your kitchen on my Elfin and it worked well except for implantxip, because i've reduced the size of my XIP partition in template payload, so implantxip gave me error like "no xip section found". i replaced implantxip with msflshtool and it worked fine. no other issues faced in ROM building and porting newer build for my Elfin . although i had to make some adjustments to Dump_200.bat for dumping the ROM.
also, we used buildxip for xip porting before and it had some specific switches like -g, -k and -f useful for enabling different kernel modes, changing fsrampercent etc. i was wondering if same is possible while xip porting with new kitchen or is the best setting chosen automatically?
and, do check your paypal for Transaction ID: 45A49499TS934251W
I made a kitchen for the Herald that creates ROMs in both XPR and LZX compressions and I was wondering if you guys wanted it ported to your phones?
If you want it, I need a few things. This ROM is compatible with Bepe's Extended ROM kitchen. It won't come with OEM, ROM or XIP folders as you can get those yourselves.
The way the kitchen work is:
Run "RunMe.bat"
Choose compression algorithm. (XPR or LZX)
Follow the normal Bepe's kitchen process.
Wait as the kitchen creates the ROM (like Bepe's kitchen, but with whatever compression you chose.)
The kitchen will automatically open up the imgfs.bin in a hex editor and automatically adjust it for the wanted compression before it builds the ROM.
It automatically inserts the proper XIP drivers.
It will automatically set the Pagepool to 4MB but give you the option to change it to something else as it does.
It then automatically creates the NBH and then finally launches whatever flasher (CustomerRUU, FlashCenter, or whatever your devices use) to flash the ROM.
For those who don't know what LZX compression is:
It's a compression algorithm that, although slower (by 1-4% in real life use) gives a good amount of free storage space. In some case (like in the Herald) it makes the ROM so small that it has to be flashed through an SD card due to the Herald's flashing size requirements. On an average 50mb ROM, it takes off about 10mb. The actual cooking itself does take a LOT more CPU and RAM to do in your PC, though. Especially the RAM. (It's because the tools that actually do the compression weren't really optimized for the job.)
Anyhow, let me know if you want it.
this sounds good. would it work with wm6.5 roms?
FCW said:
this sounds good. would it work with wm6.5 roms?
Click to expand...
Click to collapse
It should. ^_^
ivanmmj said:
It should. ^_^
Click to expand...
Click to collapse
id love to see this. just had a look it the one in your sig and im impressed with how easy it seems to use. not cooked anything using it tho after all its not for hermes yet. would come in handy for my next rom. im experimenting with home 2 but it uses a lot of ram. more than m2d
another question
would it work with the newer bepe kitchen. i notice your herald version uses an older one. would it work copying the newer one into the working folder.
FCW said:
id love to see this. just had a look it the one in your sig and im impressed with how easy it seems to use. not cooked anything using it tho after all its not for hermes yet. would come in handy for my next rom. im experimenting with home 2 but it uses a lot of ram. more than m2d
Click to expand...
Click to collapse
That's not the LZX kitchen. That's an OLD and very broken kitchen. I should update my sig. ^_^
FCW said:
would it work with the newer bepe kitchen. i notice your herald version uses an older one. would it work copying the newer one into the working folder.
Click to expand...
Click to collapse
I've already ported it to the Keiser using Bepe's newer kitchen so yes, it is possible. The Herald was left behind in the dust when it comes to new kitchens go. I've been porting the newer kitchen to the Herald but I haven't finished it.
FCW said:
would it work with the newer bepe kitchen. i notice your herald version uses an older one. would it work copying the newer one into the working folder.
Click to expand...
Click to collapse
Copying it over wouldn't work. The kitchen in my sig is OLD. The new kitchen requires a lot of scripting modifications to the kitchen. It's not a drag and drop kind of thing.
So, what do you need?
HEre is my Hermes kitchen based on new bepe if you want to work on that for everyone it's 6.5
ivanmmj said:
Copying it over wouldn't work. The kitchen in my sig is OLD. The new kitchen requires a lot of scripting modifications to the kitchen. It's not a drag and drop kind of thing.
Click to expand...
Click to collapse
still very interesting. im happy to test if you need a guinni pig lol
Sorry, I've just been pretty busy. I'm gonna take that kitchen you linked and modify it later today, probably. ^_^
joshkoss said:
HEre is my Hermes kitchen based on new bepe if you want to work on that for everyone it's 6.5
Click to expand...
Click to collapse
If it's anything like your kaiser kitchen, it'll be very simple to modify as I already have the code from your kaiser kitchen and I won't have to modify it too much.
ivanmmj said:
If it's anything like your kaiser kitchen, it'll be very simple to modify as I already have the code from your kaiser kitchen and I won't have to modify it too much.
Click to expand...
Click to collapse
it is based off the same thing... just putting it up for anyone so you can modify
Ok, I'm done modifying the kitchen.
I need someone to test the ROM to see if it boots before I release the kitchen.
The ROM was decreased from 59,145KB to 48,983KB. That's a little over 10MB saved.
I'll post the link to the upload once it finishes uploading.
I'll definitely test it once you get it uploaded
I'm having problems with the connection in my current location so I haven't been able to upload it. I'm sorry. I'll keep trying until it gets there.
Here it is!
ivanmmj said:
Here it is!
Click to expand...
Click to collapse
i got 6 min till its downloaded ill test and get back to you so we should know if it works within the next 30 min
FCW said:
i got 6 min till its downloaded ill test and get back to you so we should know if it works within the next 30 min
Click to expand...
Click to collapse
Sounds great!
Same here! Will let you know when it's done flashing
im new to this cooking thing and wanted to make sure of somethings.
1. what exactly goes into the SYS folder? i read somewhere on the forums that the only folders needed in this folder are the .ROM, .VM, and the shell folder with the shell32 folder is all that is needed in there. is this true.
2. does the my programs and games i want to cook into the rom go in the OEM folder after i use the cab2oem program? oh yeah and where do i put the cab files that dont want to seem to convert?
3. what would i need to make my rom a RBSC rom and how do i get rid of the ULD partition?
4. where would i put the files in for like the different shells so that it starts up on these shells after it is flashed like for example: the iphone shell or http://forum.xda-developers.com/showthread.php?t=354866&highlight=SCLPF
I think thats about it. Oh and before you start scolding me and say "its called a search box" or "maybe you should look"...well just know that i have and cant find anything. I have been seeking these answers for about three days now.
Many answers to wich i know the meaning and knowledge...
1.-In sys folder goes all the OS Base...
What do i mean by this? well it depends on the kitchen you use... if ou can see on the kitchen of Josh its a modified kitchen betwen ervius visual and bepes platform rebuilder so not so much folders in it! the sys hs two folders more... 0409 and common... in this original kitchens you can do many lang OS or many devices OS, so thats why there is more folders than OLD School way... so there are so much folders in it like the office... the bronzeres the manilla 2d and many more...
in old school the OEM folders becomes sys when dump again the rom so imagine how many things must be on SYS!!!
the .rom .vm and shell and shell 32 is a way to port the sys... but is not ported well with this method. and yes that folders must be on SYS anyways.
2.- Yes exactly the programs you wish to add to the rom must be on OEM folder... and the cabs that dont wants to be converted into OEM must be in OEMOPERATORS to install them on first UC... you must to edit the config file like the SD config way...
3.-RBSC is related to the os.nb.payload... so get a dumped rom with RBSC and get it's os.nb.payload... and add it where this file must be... On ROM folder of the kitchen, to get rid of changing the ULD partition many people is working on it... so the modules can be added there to have more storage... wel its not so much i thing 3 MB of storage not RAM.
4.- Well dude that link is not a shell... but what do you mean by "SHELL"?
This is a program that emulates... the htc cube... that was an app too so it is not a shel but if you said you want a new theme... home plugin... or UI use them as it is a programm add it via OEM or cab thats all.
thank man that was really helpful that cleared my everyting up
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