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
Related
Just start kit. For further cooking.
Based at official release (and stable, I hope,- don't like to be beta-tester for HTC "in the dark").
It's new way for me (just began to use WinMob by Diamond), so don't bite me too much
Don't forget about Hard-SPL!
Few cosmetic changes & a little tweaked. UC ready.
In OEM left TouchFlo only.
In SYS out: OneNote, PowerPoint, WindowsLive, Help & other rubbish.
In "Install" folder - example only. You can change it to your own provider (look to OEM\CONNECTIONSETUPDB - password I found at XDA) or just use ConnectionSetup.
The most tweaks - in OEM\xxxconfig
Be careful to finish.xml - it's important file!
(return to "Internal Storage". Manila start including in this file too. You can customise it up to you. Same as *.rgu in this folder)
To find the bugs&errors better together, I think
Ideas&remarks - welcome!
It's OPEN PROJECT.
Kitchen: http://rapidshare.com/files/143594363/WWE_1.93.479.3_kitchen.zip
Example ROM (with pass for provision.zip):
http://rapidshare.com/files/143600258/1.93.19965.Light.rar
For make the same - just press !COOK.CMD in the kitchen.
Lighted packages:
http://rapidshare.com/files/144298572/PACKAGE_Diamond_PhoneCanvas.RAR
http://rapidshare.com/files/144138802/PACKAGE_Diamond_QuickGPS.RAR
The trick - in change heavy bmp files to compressed/indexed png.
And patched dll/exe, for use another files.
Not sure about using system resources in this way - up to you. Try.
Changes: http://rapidshare.com/files/144298443/changes_to_kitchen.rar
(Corrected ROM container: 19965 now. Was 20273 - just mistake. And help engine)
can I just install your rom on my Diamond?
Would like to try it, but dont want to fool around with the Kichen stuff
Been reading much on cooking the last days. This looks like a good start!
Thanks for sharing. Hope I can create my own Diamond ROM from here. If it's good enough for some of my friends I will share it on XDA as well
teddyen66 said:
can I just install your rom on my Diamond?
Click to expand...
Click to collapse
Not see the reason - only base functions.
You are right, but it's the fastest ROM I've ever tried
But like you said, it's very basic. Camera is not working, so you need to add all these yourself.
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
It does seem to extract just normal. Is the RAR file save?
update: You might even remove the Office part from the light ROM??
mccune said:
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
Click to expand...
Click to collapse
Hm. "Top" level - zip. Inside - rar. Going to try download back. May be corrupted...
No, everything OK to archive.
I use rar v.3.71
mccune said:
You might even remove the Office part from the light ROM??
Click to expand...
Click to collapse
Word & Excel till alive
mccune said:
You are right, but it's the fastest ROM I've ever tried
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
It does seem to extract just normal. Is the RAR file save?
Click to expand...
Click to collapse
Its 7-Zip i think extracts ok
I will give this a try, other kitchens didn't work out for me very well.
Thanks man ...
Help system
I think idea to remove the help system absolutely is not the best.
Sometimes apps need it for normal work. May keep help engine alive?
Any opinions?
Please tell me one usefull hint that's provided to you because of the Help function?
For me it's wasted space on every device I've owned. If I encounter any problem they go beyond the help files
Looks pretty complicated with no real guide, will look into other kitchens!
I talk about engine (hwhelp) only. The most help files - "dead cargo", of course.
After try to push "help" button at some apps - error, could make system unstable.
P.S. made two "light" packages. ( see in the first post).
It use a little less memory, I hope.
Congratulations for this new project! If you need any help about a multilanguage (Italian) version... I'm ready!
sev7en said:
Congratulations for this new project! If you need any help about a multilanguage (Italian) version... I'm ready!
Click to expand...
Click to collapse
Thanks for support
I think, change the locale - it's only change the *.mui & may be other files in folders *_0409. Change to Italian locale - _0***, don't know exactly.
Could you try it?
Found the mistake - "alien" rom container (from 20273) in the kitchen.
Just accident.
May be it's nothing, but...
- in the first post + hwhelp.exe: changes_to_kitchen.rar
Tricks
Stop unused services (functional don't loose) - will start on demand:
[HKEY_LOCAL_MACHINE\Services\BTAGSVC]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\BthAsPlugin]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\BTHIDSVC]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\OBEX]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\QuickGPS]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\WirelessService]
"Flags"=dword:00000004
It's THE SAMPLE. (but I use it)
May stop any more? Biotouch, for example?
------------------------------------------------------------------------
Start HTCVolumeControl.dll without taskmanager, or if you use another TM:
[-HKEY_CURRENT_USER\Software\HTC\BootLauncher\Services\HTCVOLUME]
[HKEY_LOCAL_MACHINE\Services\HTCVOLUME]
"Dll"="HTCVolumeControl.dll"
"Order"=dword:0000000c
"Index"=dword:00000000
"Info"=dword:00000000
"Prefix"="VOL"
Tested on Raphael VolumeControl
------------------------------------------------------------------------
Somebody can explain how to (EXACTLY! step by step) change OS, XIP, SYS in this kitchen? I've read a lot of tutorial but I didn't understand how...
In example, I've got:
1) this kitchen and this "base" rom
2) another diamond rom with 20748 xip build.
If I would to update OS, XIP and SYS to newer, what I have to do?!
GriFolle said:
Somebody can explain how to (EXACTLY! step by step) change OS, XIP, SYS in this kitchen? I've read a lot of tutorial but I didn't understand how...
In example, I've got:
1) this kitchen and this "base" rom
Click to expand...
Click to collapse
You don't neet "base" rom (or what you mean?) it's example only.
If you talk about rom\os.nb in the kitchen - it's just container for rom, which is empty.
GriFolle said:
2) another diamond rom with 20748 xip build.
If I would to update OS, XIP and SYS to newer, what I have to do?!
Click to expand...
Click to collapse
Just delete oem, rom, sys & make you own "tree"
Thanks for your very QUICK reply Modilv!
So, I have just to take the parts of (maybe more) diamond romS that I need (including OS.nb??) and put theme in your kitchen..?
So simple?!
PS: no "porting" xip or something like that?
TIA
It't not "my" kitchen (just add bepe's utility to final step)
I made the "tree" only.
You can do the same.
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
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
[KITCHEN+ROM][WWE]Stock Diamond 2.03 Kitchen & Rom ported with 21042XIP/SYS (Online)
I've seen a few requests for kitchen's & rom's based on 21042 XIP/SYS so I decided to knock one up using the 2.03MRII 2.03.401.3 base and XIP/SYS from 21042 build.
This kitchen & rom is currently completely stock. Nothing removed from the OEM & SYS folders, no tweaks no addon programs just standard diamond build with newer core.
The only extra included which isn't in the original stock rom is remote desktop mobile (came with the sys not an extra) which of course you can remove from the kitchen if you wish. As it's the new sys it obviously contains the newer builds of MS apps including Windows live. Also this does not have the newer version of IE, just standard version.
Keyboard currently supports English, French, German, Greek, Italian & Spanish t9 however this should be updatable with the 14 language patch available elsewhere.
The kitchen is bepe platformrebuilder in almost stock form. No extra tools except for it runs htc rom tool to build the nbh file at the end.
XIP is not changed in anyway except updated msxipkernel & msxipkernelltk from 21042. No pagepool patching, cert patching or time/date/name changes. os.nb.payload size is reduced in the kitchen however this has no bearing on the final rom.
As this uses bepe's platformrebuilder, if you wish to change the date, build, pagepool, cert patching in the kitchen directly, these need to be done on nk.exe in the oemxipkernel. Any changes made to os.nb.payload (except uldr) will not be carried forward to the final rom as the nk.exe will overwrite changes to the payload. The payload itself is not ported so if you extract this and replace the msxipkernel folders then you will be back to a 20764 xip. There is no need to port the payload as replacing the msxipkernel & ltk folder in the xip folder properly ports the xip anyway if you are using bepe's kitchen (surface kitchen does not work properly in this way)
Also any rom's built with this tool are automatically locked as the kitchen deletes rgu's & dsm's from the cooked rom for space saving and performance. The files are extractable but then all you get is a dump of the files, without being able to seperate to packages.
Hope this helps some of you out there.
Also on the link there will be a stock diamond rom built from this kitchen - entirely stock but with latest xip/sys - even .netcf is still v2.0 that's how stock it is. It does however have more storage memory as it is cooked - original has 82Mb total and 57 available - this has 102Mb in total and 75+Mb free. Using the kitchen you could make a rom with alot more free space however.
I would recommend atleast upgrading .netcf to 3.5 in this rom if you are lightly cooking. Package for this is available on the forum
If you release a rom using this kitchen, please do not forget to credit the source.
Shaks.P Roms are free and always will be. If you like my Roms optionally send me a drink here:
Download Links:
http://diamond.geg0r.de/index.php?dir=Shaks%2FStock%2F
Please donate to bl0w for providing this mirror.
Important: Hard spl is required to use either the rom on this link or any rom created with this kitchen.
Basic Tutorial
As the rom is already ported & extracted, all you need to do is make your modifications then build the rom.
Step 1. Modify the sys & oem folders with the packages that you need. Make a backup of any folders you delete in case they cause issues with anything else.
Step 2. Once you are happy with the modifications, run build_rom.bat. This will create the os_new.nb file in the root of the kitchen folder. Once this is done, it will load the htc rom tool that builds & signs the final nbh file.
Step 3. Once the htc rom tool loads, select Build!, Change the version to anyversion you would like (this version only shows up when flashing). Under system, click on ... and select the os_new.nb file that has just been created. Then click on Build! ROM and this will ask where to save the nbh file and the name. Save as diamimg.nbh if you want to flash thru internal storage or any other name you like if using customruu.
Step 4. Ensure your device has hardspl, then flash the rom you just built either using custom ruu or using the internal storage method. If it doesn't work, you can allways flash another rom after getting the device in bootloader mode.
Can't wait
Thanks!
Will you post it today, or....?
And can i make my rom from this "Rom ported with 21042XIP/SYS"?
Thanks!
alxalx said:
Will you post it today, or....?
And can i make my rom from this "Rom ported with 21042XIP/SYS"?
Thanks!
Click to expand...
Click to collapse
It's uploading at the moment. It is a seperate kitchen & a rom as well. You can make whatever type of rom you wish to with this. Just mention the original source if you release it.
The rom is if you want a stock rom with the new build. Looks like you need the kitchen. Should all be uploaded in next 15-20 mins. Had to start the upload again.
Thanks shaks!
Not only do you provide the best ROM around, but now also a kitchen, you rock!
sweat shaks thanx for sharing going to finaly try my own Rom you make us happier and happier every time
(EDIT)
so does this mean your not going to build any more Roms or ?
shaks1979 said:
It's uploading at the moment. It is a seperate kitchen & a rom as well. You can make whatever type of rom you wish to with this. Just mention the original source if you release it.
The rom is if you want a stock rom with the new build. Looks like you need the kitchen. Should all be uploaded in next 15-20 mins. Had to start the upload again.
Click to expand...
Click to collapse
Thanks man! I appreciate it!
Dynomite232 said:
sweat shaks thanx for sharing going to finaly try my own Rom you make us happier and happier every time
(EDIT)
so does this mean your not going to build any more Roms or ?
Click to expand...
Click to collapse
This is just something I felt like doing for today. The kitchen won't get updated much (probably not at all as it's not modified). The roms will continue but will be going for the long release cycles again just like 3.20. I envisage I will probably have one more release and if that doesn't have issues then no more flashing till something big happens again (maybe stable tachi rom comes)
This kitchen is so stock that it can't replace my rom without alot of work - no tweaks, extra packages or anything for that matter except what comes in the stock as that's what some people wanted and I thought it won't take long so I did it.
P.S sorry for the delay with the upload. Having some issues
damn nice to here for one more rom coming out in the near future but tell u the truth my wife went back to rom 3.20 of urs she says it was much beter for her she was used to it she will never change roms agains she says beter for me lol , but mine is doing realy fine and i gots bunch of programs installed no issues at all by the way thanks man i cant stop thanking u
Dynomite232 said:
damn nice to here for one more rom coming out in the near future but tell u the truth my wife went back to rom 3.20 of urs she says it was much beter for her she was used to it she will never change roms agains she says beter for me lol , but mine is doing realy fine and i gots bunch of programs installed no issues at all by the way thanks man i cant stop thanking u
Click to expand...
Click to collapse
Well 3.20 was a damn good, stable, time tested rom. I know a few people who won't change from it at all. Tested the latest but went back to it because they preferred it. 4.x series are a little bit more experimental but still go for the same stability. Next release should take of that small percentage who have corrupt memory/hard reset issues hopefully but I don't expect a big changelog as 4.10 is otherwise fine.
Should the bluetooth work well with this rom?
Thanks!
alxalx said:
Should the bluetooth work well with this rom?
Thanks!
Click to expand...
Click to collapse
Shouldn't be an issue - I use the same sys/xip in my rom without any issues with bluetooth.
Kitchen now online
Rom uploading now. I found if I tried to upload both at the same time, it kept stopping part way!
shaks1979 said:
Shouldn't be an issue - I use the same sys/xip in my rom without any issues with bluetooth.
Kitchen now online
Rom uploading now. I found if I tried to upload both at the same time, it kept stopping part way!
Click to expand...
Click to collapse
Thanks man, downloading now!
hi shaks when u say Modify the sys & oem folders meaning i can delete what i dont want and so on
Dynomite232 said:
hi shaks when u say Modify the sys & oem folders meaning i can delete what i dont want and so on
Click to expand...
Click to collapse
That's right - delete what you don't want, modify rgu's for packages, add your own packages e.g. using ervius package creator to turn a cab into a package or use a package already provided. You'll get lets of cooking help from here (talks about surface kitchen but basic concept the same):
http://forum.xda-developers.com/showthread.php?t=413782
Add your own packages into the OEM folder.
Downloading... In the meantime thank you!
got a question which file is it ? and can i get rid of the keyboard languages and add only the english and swedish ? if anyone
can answer plz and thank you which file is it
Dynomite232 said:
got a question which file is it ? and can i get rid of the keyboard languages and add only the english and swedish ? if anyone
can answer plz and thank you which file is it
Click to expand...
Click to collapse
Add this package to your oem folder for 14 languages & edit the line in the rgu to specify languages you want
Hi guys,
I decided to open a blog which explains how to cook roms for the i780. There are very few chefs, and cooking is a really hard science to learn without help! So, I decided that I take the time and write posts so that everyone could learn the process in a methodical manner and cook roms in the future!
I'd slowly write posts explaining each step of the process in detail, so that we can have more people learning how to cook and make the i780 community more happening
Head over to this URL to check out the first few posts -
http://i780romdev.blogspot.com
Update:
Attached core kitchen tools that you'll need to use! Enjoy!
cheers
San
I never was a fan of this forum, not sure why, maybe because I use a ASUS P527 and there are not proper instructions on how to create a custom ROM, I appreciate your taking the initiative
I think its good fun to try and figure out things on your own
Non-HTC devices do have a very small fan base unfortunately....and ironically, HTC makes the crappiest devices imo (highly crash prone, buggy, lousy drivers, useless qualcomm processor)!
You can apply the same tools and techniques even to cook asus roms....its not all that different
cheers
wooooooow thanks a lot buddy finally we have it also !!!
when will u release part 3? and also can u give the links of programs? like pkgtools_? coz i tried to download it from somewhere else and it had virus
benveq said:
when will u release part 3? and also can u give the links of programs? like pkgtools_? coz i tried to download it from somewhere else and it had virus
Click to expand...
Click to collapse
hi m8!
i'll try and upload the set of tools shortly. You can get it in any of the kitchens posted for the i780 here. I'll however consolidate them and add it in this post as an attachment!
Part 3 - very soon
cheers!
You guy thanks for sharing your experience at cook ROMS,I whink I need this for my SmartPhone.
Hey guys, just dropped the next part of the series on the blog. Check out http://i780romdev.blogspot.com
Of course, the same theory, tools and understanding goes to cook for any other device too
cheers
kitchen tools attached in the first post.
enjoy
dreamtheater39 said:
Hey guys, just dropped the next part of the series on the blog. Check out http://i780romdev.blogspot.com
Of course, the same theory, tools and understanding goes to cook for any other device too
cheers
Click to expand...
Click to collapse
yeah, now i am reading part 3 and u really teach very well! i think i will cook my own room soon with ur help i wanna ask a question if i dont want ms office and internet explorer in my rom which folders should i delete? i wanna add different office program
benveq said:
yeah, now i am reading part 3 and u really teach very well! i think i will cook my own room soon with ur help i wanna ask a question if i dont want ms office and internet explorer in my rom which folders should i delete? i wanna add different office program
Click to expand...
Click to collapse
To remove a package, you can get rid of the corresponding folders in your SYS folder. But its not recommended that you knock off office/ie as they might be referenced within other apps. You can always take it off, build a rom and see if everything works fine
For example, to remove IE, just delete your Browsing, Browsing_DPI_xx and Browsing_Lang_XXXX, BROWSINGCORE, browsingie, browsingie_LANG_XXXX folders. That should get rid of IE for you! Then you need to recreate your bin!
cheers
thanks a lot for kitchen tools and ur explanations! i read ur blog all the time great work!!
The next post is up
cheers
dreamtheater39 said:
The next post is up
cheers
Click to expand...
Click to collapse
yes i read it, and u r teaching with examples it is great
i have two problems while i am using ervius pkgtools
1. when i open dumo folder it shows
[Missing Manifests]
(Maybe):\ROM\XIP\45116509-e364-4775-9098-c25f0b1fbac2.dsm
(Maybe):\ROM\XIP\d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
(Maybe):\ROM\XIP\723fb954-d931-4348-b672-82a188e587b5.dsm
(Maybe):\ROM\XIP\1a22bb67-d4c4-7bb4-c5d2-75cb3a85c45b.dsm
(Maybe):\ROM\XIP\449da4ef-e9c1-5cb4-2ec5-fb9b4c27a865.dsm
are these important dsm files?
2. when i press build packages it gives this error:
not found: select .os file to extract XIP
and i extract xip file using osbntool as xip.bin
any solutions for both of these?
benveq said:
i have two problems while i am using ervius pkgtools
1. when i open dumo folder it shows
[Missing Manifests]
(Maybe):\ROM\XIP\45116509-e364-4775-9098-c25f0b1fbac2.dsm
(Maybe):\ROM\XIP\d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
(Maybe):\ROM\XIP\723fb954-d931-4348-b672-82a188e587b5.dsm
(Maybe):\ROM\XIP\1a22bb67-d4c4-7bb4-c5d2-75cb3a85c45b.dsm
(Maybe):\ROM\XIP\449da4ef-e9c1-5cb4-2ec5-fb9b4c27a865.dsm
are these important dsm files?
Click to expand...
Click to collapse
This is not important....ignore them, its normal
benveq said:
2. when i press build packages it gives this error:
not found: select .os file to extract XIP
and i extract xip file using osbntool as xip.bin
any solutions for both of these?
Click to expand...
Click to collapse
When you start, it asks if you would like to run build xip.bat.....just hit NO for that....
trojan reported in the attachment
Win32/TrojanDownloader.Zlob.NBP
false alarm?
well last night i finished my own wm6.1 build 20270 128dpi pdxib1 according to your guide i wanna tell what i did to complete it ;
1.i exctracted my rom using i780 kitchen and i got dump folder and i also added some extra tools like ervius buildos,osnbtool etc...then i used pkgbuildos to seperate folders into oem and sys
2. i used oem part from krizky82's kitchen and i add some extra packages using ervius package creator 2.7 and add them with oem_blahblah to oem folder.
3. i deleted windows live and msn messenger from sys folder and copied netcf 3.5 and flashlite v3.1 from krizky82 kitchen. i also used his initflash and rgu file coz i had same structure almost(oem totally same and sys programs also)
4.i looked at both efn's kitchen and krizky82 kitchen and i saw that they have this structure oem,sys and rom and in rom there is xip folder. when i looked at inside xip folder i saw that there is only coredll.dll folder and others are dsm rgu and boot files so my next step
5. i used osbn tool to exract xip.bin and after i got that xipkitchen_beta6 and i choosed the same donor and original and after extracting i got original xip files and i ordered in same structure like efn's kitchen
6.then i used pgkbuildos and let the process starti had some dsm duplicate errors and i delete duplicated ones and later i didnt start xip extract bat and flashable bin bat so after process again i had temp/dump folder
7. during buildos there wasnt any error and i was happy about it
8. using inputTXTFileMaker ( thanks to u dreamtheather93) i got input text and after that using these commands;
mgfsfromdump imgfs_raw_data.bin new_imgfs.bin
del imgfs_raw_data.bin
ren new_imgfs.bin imgfs_raw_data.bin
make_imgfs i780.nb0.payload.body -nosplit
merge i780.nb0.payload.header i780.nb0.payload.body i780.nb0.payload
nbmerge -data 2048 -extra 8 i780.nb0 -conservative
and conv3 input.txt > conv3_output.txt
ren i780.nb0.b000ff !!i780_flashable_bin.bin
i got my flashable bin file yupiiiii i controlled the size of flashable bin and it is 86.2 mb and the size of dump folder almost 125 mb i hope it is ok
now i will flash my phone but is there any possibility that my phone can be bricked ?
thanks a lot for ur guide again!!!
note: i already used i780.bin as 12mb page pool size i did it before kitchen using osbn tool
good job m8
You cant really brick your i780 because of this I've done way crazier stuff....like trying out omnia's xip, drivers of omnia on i780....and nothing's given way
However, i'm hoping you've ported your XIP accurately, and i'm unsure how've you've built your SYS folder.
but, go ahead and flash and see if it boots nothing to be paranoid if it doesnt boot/hangs at startup/throws an error and fails etc. etc. If any of this happens, then we could troubleshoot it together
cheers & good luck
Great job!
Nice start San!
Not even some days left from your first successful cooking and you already best gid on it!
Keep on do it. And we wait for new mods for our best touchphone!
I think now anyone is able to break Eagles wings =P