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
Related
New extended Kitchen for Artemis
ARTEMIS_DEV_v2.1_Build_19199.rar
Related:
Extended Kitchen for Trinity
Extended Kitchen for Hermes
Extended Kitchen for Herald
Thanks to misar, FreePK for helping with this new set of tools!
About the Kitchen
Artemis base: HTC P3300 WWE 3.13.405.1
OS base: VF Kaiser UK 3.08.161.0 (Build 19199)
OEM Apps removed, but you need to clean up the OEMDrivers package
I did not do any changes to the OS, because it should be a clean base Kitchen for all of you
Full XIP editing supported by the Kitchen
New tool to merge all dsm files to one big file and delete all rgu's
I think the OEM package to SYS problem should be solved... but did not try it yet
How to use it
Requires Microsoft Visual C++ 2008 Redistributable Package
OEM and SYS can be used as known
The content of ROM\XIP will be used to create a new XIP section for the OS
You don’t have to worry about relocating modules... add/remove whatever you like and the new tools will take care of relocating modules or freeing RAM
.VM and .ROM is updated automatically
Actually this Kitchen runs in auto mode, which means you only need to run BuildNB.bat to create the ROM. You can change that by editing the bat files; made it this way, because I don’t use the options in BuildOS.exe
I consider this a perfect port of the new build to this device
Replaced all XIP SYS packages (I did not just changed coredll.dll to get the new build number)
There were also boot.rgu changes my MS, those have been added too
SYS is completely untouched
Read this for download:
All donations are very welcome!
I need to buy a new device, because this time my Trinity is gone forever and I cannot use my girlfriends Artemis without being killed (by mistake I deleted all contacts last time I used it for testing... she was not very happy about that )
When you are getting money for the ROMs you cook using my kitchen, I would really appreciate a donation.
I'm not talking about 50% of you incomes, but one small donation would be fair I think.
To download the Kitchen click at "All donations are very welcome"
!!! This was only meant for ppl never donated for these tools and expecting donations for ROM's created using my Kitchen !!!
Thanks to all those who have donated already!
Happy cooking!
bepe said:
Could someone please try this Kitchen, cos I dont have any device right now...
http://rapidshare.com/files/88860516/ARTEMIS_DEV_v2.1_Build_19199.rar
Related links:
Trinity: http://forum.xda-developers.com/showthread.php?t=364634
Hermes: http://forum.xda-developers.com/showthread.php?t=363721
Click to expand...
Click to collapse
Thanks bepe will give it a try and let you know
I'm on it too.
TNX!
bepe said:
Could someone please try this Kitchen, cos I dont have any device right now...
http://rapidshare.com/files/88860516/ARTEMIS_DEV_v2.1_Build_19199.rar
Related links:
Trinity: http://forum.xda-developers.com/showthread.php?t=364634
Hermes: http://forum.xda-developers.com/showthread.php?t=363721
Click to expand...
Click to collapse
Thanks bro
What does this Ext. ROM contains? Will it be suitable with BB5.0?
meschle said:
Thanks bepe will give it a try and let you know
Click to expand...
Click to collapse
I CONFIRM IT WORKS - MANY THANKS BEPE - I MADE THREAD A STICKY
it works here too!
EazyVG said:
What does this Ext. ROM contains? Will it be suitable with BB5.0?
Click to expand...
Click to collapse
Sorry about that... did not see that the name might be confusing...
It means that this is a ROM Kitchen with an extension to edit/build XIP sections
To edit the XIP section was no easy task until now, so this means a little revolution for porting new build to our devices.
meschle said:
I CONFIRM IT WORKS - MANY THANKS BEPE - I MADE THREAD A STICKY
Click to expand...
Click to collapse
NikMel said:
it works here too!
Click to expand...
Click to collapse
Thanks to both of you, great that it is working, happy cooking
Thanks bepe
Nice and great tools for Artemis.
thanks you so much.
dheewatara said:
Nice and great tools for Artemis.
thanks you so much.
Click to expand...
Click to collapse
P' Dhee ,Could you please make a tutorial ?.
Many thanks to Bepe for making the new toy
I tried several times building a rom using the kitchen but failed. What I did was simply put in OEM packages and build the OS, got a nb file, then used htcrt.exe to convert it to a nbh for flashing. Everything seems fine during the flash. But when it restarts it dies in the first splash screen.
Any hint for this?
mypleasure said:
I tried several times building a rom using the kitchen but failed. What I did was simply put in OEM packages and build the OS, got a nb file, then used htcrt.exe to convert it to a nbh for flashing. Everything seems fine during the flash. But when it restarts it dies in the first splash screen.
Any hint for this?
Click to expand...
Click to collapse
First try if a ROM without OEM packages is working, next you need to add one OEM package after another... I'm sure there is something wrong with one of the packages.
You are using the wrong drivers.
Do you any drivers installed??
Did you fill XIP up?
mypleasure said:
I tried several times building a rom using the kitchen but failed. What I did was simply put in OEM packages and build the OS, got a nb file, then used htcrt.exe to convert it to a nbh for flashing. Everything seems fine during the flash. But when it restarts it dies in the first splash screen.
Any hint for this?
Click to expand...
Click to collapse
Great. Will come up with some cooked stuff soon
Regards,
Carty..
Built a ROM without addidng anything but a music file to reach 50MB limit but the ROM never passes the splash screen on device. The same happens with extracting and re-building of cooked ROMs even without editing. What am I doing wrong?
But when I extract and rebuild an OEM rom, everything works fine!
Regards,
Carty..
NikMel said:
You are using the wrong drivers.
Do you any drivers installed??
Did you fill XIP up?
Click to expand...
Click to collapse
Thank Bepe and NikMel a lot for your kindly help.
Should I keep the drivers in the kitchen, or replace them with the drivers from wm6.0? And how to fill the XIP? Sorry I am a newbie to the kitchen.
Most of the ROM do not include the rgu files.
You need rgu files to make your own rom.
Carty said:
Built a ROM without addidng anything but a music file to reach 50MB limit but the ROM never passes the splash screen on device. The same happens with extracting and re-building of cooked ROMs even without editing. What am I doing wrong?
But when I extract and rebuild an OEM rom, everything works fine!
Regards,
Carty..
Click to expand...
Click to collapse
the easyst way is to copy "OEMDrivers" map from wm6.
You should copy XIP files one by one from other rom and put it in a map with the same name.
mypleasure said:
Thank Bepe and NikMel a lot for your kindly help.
Should I keep the drivers in the kitchen, or replace them with the drivers from wm6.0? And how to fill the XIP? Sorry I am a newbie to the kitchen.
Click to expand...
Click to collapse
NikMel said:
the easyst way is to copy "OEMDrivers" map from wm6.
You should copy XIP files one by one from other rom and put it in a map with the same name.
Click to expand...
Click to collapse
Thx again NikMel, these hints should be able to get me going...
What is the map you guys talking about? Where do i find it?
Regards,
Carty..
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.
gee,
that sounds great - i aint having spare time to get involved in cooking,
...but all cooks, come on , this is a great opportunity, aint it?
greetz
Could be interesting indeed, even though i never encountered the problem of not having enough storage room.
What is more interesting to me, is to know that if you flash through the SD you don't have the 50mb limit
Sorry I am newbie in rom cooking.
Anyone can share how to actually start to cook a own roms??
thanks
Sorry I am newbie in rom cooking.
Anyone can share how to actually start to cook a own roms??
thanks
dioooi said:
Sorry I am newbie in rom cooking.
Anyone can share how to actually start to cook a own roms??
thanks
Click to expand...
Click to collapse
Hi dioooi,
You can find some infos about cooking here and the kitchen here.
Learning how to cook is a long and difficult proces. I'm just playing a little around with some roms but it takes a lot of time and reading.
Good luck
[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
I'm working on making my SuperJustKitchen the support the Hermes and I need someone to test this sample ROM. It's not perfect, yet, or anywhere near it, but I want to know if it at least boots.
http://justkitchen.info/JustROMs/HermesTest.7z
Today is "my flashing day"! .... tested quickly .... it boots!
Woot! That's two boots so far. I just have to clean the OEM a little more and I will be releasing SuperJustKitchen v0.7 with official Hermes support.
ivanmmj said:
Woot! That's two boots so far. I just have to clean the OEM a little more and I will be releasing SuperJustKitchen v0.7 with official Hermes support.
Click to expand...
Click to collapse
Sounds good..I'm always looking to try a new kitchen.
Cool!!!! does this kitchen supports Native kernel6.5? multieverything?
jejeje thanks Ivanmmj! will be waiting for it... you have here another betatester.
Keep it up!
I can only give you guys a native 6.5 kernel if you guys already have one.
Do you?
Yes we already have Native! 6.5 nk
Give me a link and I will include it (although most of the kitchen files have already been converted to files to work with the other devices.)
ivanmmj said:
Give me a link and I will include it (although most of the kitchen files have already been converted to files to work with the other devices.)
Click to expand...
Click to collapse
hi ivanmmj!!!
here is link WM 6.5 Native Kernel/nk.exe/xip.bin for Hermes
It looks like the download link is down. Does anyone have it and can they mirror it?
ivanmmj said:
It looks like the download link is down. Does anyone have it and can they mirror it?
Click to expand...
Click to collapse
I can get it to you when I get off work if you don't have it already. What do you need just the OEM*** folder that has nk.exe?
The NK should be in the XIP, so I need your OEMKernelXIP, although having your OEMDrivers probably won't hurt, either since it has newer drivers. (IF the OEM is new... I don't know if it is or if only the XIP is new.)
ivanmmj said:
The NK should be in the XIP, so I need your OEMKernelXIP, although having your OEMDrivers probably won't hurt, either since it has newer drivers. (IF the OEM is new... I don't know if it is or if only the XIP is new.)
Click to expand...
Click to collapse
Sorry thats what I meant the OEMkernelXIP folder I just didnt remember it off the top of my head.
I can give you my OEMDrivers also just in case.
ivanmmj said:
It looks like the download link is down. Does anyone have it and can they mirror it?
Click to expand...
Click to collapse
here:
http://forum.xda-developers.com/showpost.php?p=4045792&postcount=31
caxio said:
here:
http://forum.xda-developers.com/showpost.php?p=4045792&postcount=31
Click to expand...
Click to collapse
I had a problem with that one since its set to 15pp. The one I use is still by utak3r but has the correct pp set.
It's ok. By default the PP will always be set to 6mb on the kitchen and you can change it with a simple option.
Mind you, from now on, you will have to click on the "native 5.6 kernel" option from here on in the kitchen.
just in case
http://www.4shared.com/file/144724764/f441f2f/drivers_kernel.html
I haven't download the second link, yet, but here's a test made with the first link. It's just random programs put together. (I'm still working on stripping the OEM's of the Hermes, the Artemis and the Opal for the next kitchen release.)
http://justkitchen.info/JustROMs/HermesTest2.7z
EDIT: Forgot the link. lol
Just as Info....
The kernel that Da_G posted has PP in 15mb and the EVK xiporterexe cant change the PP, but utak3r stripp even more the native kernel... and makes it change with the nbtools.exe.. so our .bat in EVK change in the line to allow nbtools change the pp.
+ Que PPC said:
Just as Info....
The kernel that Da_G posted has PP in 15mb and the EVK xiporterexe cant change the PP, but utak3r stripp even more the native kernel... and makes it change with the nbtools.exe.. so our .bat in EVK change in the line to allow nbtools change the pp.
Click to expand...
Click to collapse
Can you provide me with a link to the program and instructions on how to use it to change the pagepool?
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