Related
I've been thinking lately... I've been thinking of creating a new multidevice kitchen. The kitchen would support every current device, be based on the newest version of Bepe's kitchen or maybe the visual kitchen. It would add certain things like:
Automatically insert the cecompr.dll needed for both LZX and XPR compressions
Automatically hex edit the imgfs.bin during the cooking process to allow to LZX compression
It would come with an empty payload file for every device
It would support multiple languages and come with language packs
It would use the standard layout of bepe's kitchen/the visual kitchen so it would be easy to also keep build packages that would apply to every kitchen.
If I could get enough cooks involved from other devices, we could even have base STRIPED OEMs from every device that people can easily download.
We can make it automatically be able to dump any ROM and easily extract its XIP or SYS and import them into the kitchen or make the files into a package compatible with the kitchen that people could upload for everyone else to use. (Easier to spread new builds leaked by other people.)
I need more ideas as to what we could make this kitchen do.
I also need to know if any cooks would be willing to help out as it would be a MASSIVE project.
I would start it as soon as I'm done with two ROMs that I'm currently working for and a few kitchen that I'm modding for some people for LZX/XPR multicompression.
No comments, yet.
I'm working with ervius to add the LZX compression to the kitchen itself.
If no one helps, then it's going to be a little hard to do since I will have to download the default ROM for each and every device and then strip down the OEM. Then create bigROM packages to release as well. And then I can't test it since I don't have every device, so it's going to be a little bit of a slow process.
What I will end up doing will be more like just taking ervius kitchen, add a few things here and there and make all the packages and builds and whatnot available. Or at the least create a thread where people can post packages left and right. A repository of sorts. (A lot like the PPCgeeks's BuildOS but compatible with every device and using ervius awesome kitchen.)
Sounds like what Anchilus had one time! I think it was named as hypercore. But great idea though. I am not an expert cook or programmer, but I do cook ROM for myself sometime. My biggest thing is porting the ROM, doesnt matter what tutorial I read, I just dont get it LOL
Take a look in the raphael forums. Already done.
Will Help You
Ivan,
You know that I am willing to do anything I can to help you. Problem is that we have the same devices and you are my mentor so I am not sure how much help I would be, but whatever you need, you name it and I will do my best to help you out however I can.
GSLEON3 said:
Take a look in the raphael forums. Already done.
Click to expand...
Click to collapse
I looked. I couldn't find a multidevice kitchen...
GSLEON3 said:
Take a look in the raphael forums. Already done.
Click to expand...
Click to collapse
I think you mean this? http://forum.xda-developers.com/showthread.php?t=505800
Would be a great idea one kitchen for all devices, although I think the extra devices should be added in the form of plug-in, because nobody likes to dl a 20 GB kitchen . I would help but I'm not that great at dumping but especially not with the still changing structure of ervius visual bepe's kitchen. Is there a wiki or tutorial somewhere that properly explains where to put which folders? 12
Yes, it wouldn't include all the devices at once. The aim of the project is to provide plugin packages for every device. A standard repository of oem packages (divided by QVGA, VGA, WVGA, etc), a standard repository of SYS and XIP builds, and a standard set of stripped down OEMs from different devices. Everything would be downloaded seperately. It's a huge project, that's why I would need lots of help.
EDIT: Just read that link. Kind of like that, but for multiple devices. Including language packs and all.
ivanmmj said:
Yes, it wouldn't include all the devices at once. The aim of the project is to provide plugin packages for every device. A standard repository of oem packages (divided by QVGA, VGA, WVGA, etc), a standard repository of SYS and XIP builds, and a standard set of stripped down OEMs from different devices. Everything would be downloaded seperately. It's a huge project, that's why I would need lots of help.
EDIT: Just read that link. Kind of like that, but for multiple devices. Including language packs and all.
Click to expand...
Click to collapse
To get the attention of the cooks I think you should start sending email to the chefs and maybe a couple of mods too. I don't think it should be much of a problem on the raph forum, we are blessed with kind and sharing chefs, 12
i would love to help out with the kitchen.
although, i dont like bepe's way of cooking as much as the old way
multi-device sounds great, like in the days of hypercore
mbarvian said:
i would love to help out with the kitchen.
although, i dont like bepe's way of cooking as much as the old way
multi-device sounds great, like in the days of hypercore
Click to expand...
Click to collapse
You can use my kitchen (based on visual kitchen) to add more devices but someone should develop a kind of frontend app to have ability to download only desired build, device OEMs, VGA/QVGA etc (manual selection will be a nightmare for normal users) . I can help in building such a kitchen but I can't write app, sorry
ivanmmj said:
Yes, it wouldn't include all the devices at once. The aim of the project is to provide plugin packages for every device. A standard repository of oem packages (divided by QVGA, VGA, WVGA, etc), a standard repository of SYS and XIP builds, and a standard set of stripped down OEMs from different devices. Everything would be downloaded seperately. It's a huge project, that's why I would need lots of help.
EDIT: Just read that link. Kind of like that, but for multiple devices. Including language packs and all.
Click to expand...
Click to collapse
qsqa said:
You can use my kitchen (based on visual kitchen) to add more devices but someone should develop a kind of frontend app to have ability to download only desired build, device OEMs, VGA/QVGA etc (manual selection will be a nightmare for normal users) . I can help in building such a kitchen but I can't write app, sorry
Click to expand...
Click to collapse
You mean like an kitchen appstore or a bat to move everything into the right folders? 12
That's a great idea. An app that automatically downloads the needed files just for your device type of thing... I'm not a programmer, though.
I want this to also have language packs that modify the language of the ROM.
Let this be the kitchen to rule all kitchens.
ivanmmj said:
That's a great idea. An app that automatically downloads the needed files just for your device type of thing... I'm not a programmer, though.
I want this to also have language packs that modify the language of the ROM.
Let this be the kitchen to rule all kitchens.
Click to expand...
Click to collapse
i agree, this would be a very great idea. I think ppcgeeks has something similar with their BuildOS kitchen
p.s. ivan, while you're here, could you answer this question for me?
ivanmmj said:
Replace the FIRST one and FIRST ONE ONLY with "LZX". Save the file, close the hex editor. Let your kitchen do it's thing.
That's it.
http://www.4shared.com/file/101370353/b7650aff/Compression.html
Click to expand...
Click to collapse
do we need to do this step on the "mythical" cecompr.dll?
thanks
mbarvian said:
i agree, this would be a very great idea. I think ppcgeeks has something similar with their BuildOS kitchen
p.s. ivan, while you're here, could you answer this question for me?
do we need to do this step on the "mythical" cecompr.dll?
thanks
Click to expand...
Click to collapse
Already answered there.
But,
Yes.
The cecompr.dll is what tells the XIP how to read the LZX compressed imgfs.bin. The hex editing is what tells the kitchen tools to write the imgfs.bin in LZX compression.
I worked with evirus and now his kitchen has an option for LZX compression. It will do everything automatically. ^_^
That's a great idea. Not sure it could work on my device (ks20) as bepe's kitchen crashes on my nk.exe so I have to build xip part the old way (using xipport). Anyways, if you need french 96dpi resources, I can give you mine.
And for this project, instead of a special software to download packages, why not using a svn repository ?
Although a SVN repository would be awesome, I wonder if there would be a legal problem just like there was with the XDA FTP server used to host ROMs and stuff for building ROMs?
Yes, that's possible... perhaps we should ask a moderator, what was the exact reason it was removed (because after all, everything is still present on this forum, it's just not grouped in 1 place, but I think legal issues remain).
I also know that somewhere on the web, there is a svn server for winmo builds (I had once a wm build that had .svn folders).
Ivan, You can use my site to host your files, repositories, and current roms. I can alot you as much space as needed and even a .info domain name if you like. It will be hosted on the the same host as mycw.info (My gf's site for our chickens and stuff.) PM me or just respond on this post.
DestructDez1 said:
Ivan, You can use my site to host your files, repositories, and current roms. I can alot you as much space as needed and even a .info domain name if you like. It will be hosted on the the same host as mycw.info (My gf's site for our chickens and stuff.) PM me or just respond on this post.
Click to expand...
Click to collapse
PM sent. Thank you!!
Well, I guess I will contribute with something...
There are way too many kitchens out there (all scattered in the different device forums). Now, since this is "Chef Central", I figured that we needed the kitchens for the Chefs to cook. Without further ado, I present you with... the kitchens.
[highlight]PPCKitchen.org:[/highlight]
Easy to use for the beginner...
http://www.ppckitchen.org
[highlight]Ivanmmj SuperJust Kitchen (thanks +QuePPC and kokotas):[/highlight]
Multi-Device Kitchen
http://justkitchen.info/main/index.php
[highlight]osKitchen:[/highlight]
New kitchen based on bepe's work (thanks mwalt2)
http://forum.xda-developers.com/showthread.php?t=628948
[highlight]Ervius Visual Kitchen (EVK)thanks mwalt2)[/highlight]
http://forum.xda-developers.com/showthread.php?t=469420
[highlight]Wallaby (Peter Poelman):[/highlight]
http://forum.xda-developers.com/showthread.php?t=219037
[highlight]Blue Angel:[/highlight]
Latest: 28230 by sun_dream
http://forum.xda-developers.com/showthread.php?t=428030
Swampy395 Porting Kitchen
http://forum.xda-developers.com/showthread.php?t=587446&highlight=porting
[highlight]Himalaya:[/highlight]
Latest: 28230 by sun_dream
http://forum.xda-developers.com/showthread.php?t=519129
[highlight]Wizard:[/highlight]
Not really a single kitchen but xda2_haseeb made a nice guide with links to some kitchens for the Wizard.
http://forum.xda-developers.com/showthread.php?t=501941
[highlight]Universal: (thanks orb3000)[/highlight]
ROM Kitchen v2.0 by Tomal: Next generation Kitchen for Universal
http://forum.xda-developers.com/showthread.php?t=476544
[highlight]Raphael:[/highlight]
Resources and kitchens lumped together by hilaireg
http://forum.xda-developers.com/showthread.php?t=582134
[highlight]Polaris:[/highlight]
Not really a single kitchen but cruiserrr made a nice guide with links to some kitchens for the Polaris.
http://forum.xda-developers.com/showthread.php?t=648171
Now, I am not going to scan the whole site for kitchens, so this is where we all have to pitch in. I know I am missing a few of the multi-device kitchens, but if we all contribute with kitchens for different devices, we can have a nice little resource for many new aspiring chefs...
Let's get cookin'!
Opinions
I decided to make post #2 as an Opinions Page. I will link the posts from each and every one of you that talks good or bad about a kitchen over here.
[highlight]Visual Kitchen[/highlight]
player911
[highlight]Polaris Chef Corner[/highlight]
cruiserrr
One more for the road...
NRGZ28 said:
I think we'll need to neatly catergorize these kitchen collections later on. Maybe we'll them all in the first post of this thread, or we can create another one.
Click to expand...
Click to collapse
I can update the first post as needed. I actually left two more posts after that just in case I run into space issues. I am thinking, one or two posts for device specific kitchens and one for generic kitchens. What do you think?
dXsL said:
excellent initiative, tnx!
wouldn't mind more pro's/con's per kitchen but also realize that is subject to personal experience and/or (strong) opinion
so perhaps only mention the pro's?
Click to expand...
Click to collapse
+1 on this.
PRO's/CON's can be easily worded such that it isn't considered a personal attack.
I would rather know about the CON's and how to work-around them than spend hours in trial-and-error. If a member decides to select a certain kitchen, at least they know what they are "getting into".
M2C's Worth,
* EDIT *
@egzthunder1:
BTW; if you need extra empty posts near the top of your thread, let me or another moderator know and we'll make it happen.
hilaireg said:
+1 on this.
PRO's/CON's can be easily worded such that it isn't considered a personal attack.
I would rather know about the CON's and how to work-around them than spend hours in trial-and-error. If a member decides to select a certain kitchen, at least they know what they are "getting into".
M2C's Worth,
* EDIT *
@egzthunder1:
BTW; if you need extra empty posts near the top of your thread, let me or another moderator know and we'll make it happen.
Click to expand...
Click to collapse
Thanks hilaireg, I might have to bother you regarding the extra posts if this grows as much as I fear it will .
As far as the pro/cons... well, we could do this in such a way that only people who have used the kitchens in question can post them in this thread, so they can give their points of view. I personally have had time to play with 3 of the kitchens that I have posted and used a few tools of another one, but I guess I can add this to the first post and you guys let me know what you think:
"If you are going to post a kitchen in this thread, please be kind enough to give your opinions on it (likes, dislikes, hard to use, buggy, best kitchen ever... well, you know what I mean). This way, new coming chefs will not have to go through the pain of trial and error"
egzthunder1 said:
Thanks hilaireg, I might have to bother you regarding the extra posts if this grows as much as I fear it will .
As far as the pro/cons... well, we could do this in such a way that only people who have used the kitchens in question can post them in this thread, so they can give their points of view. I personally have had time to play with 3 of the kitchens that I have posted and used a few tools of another one, but I guess I can add this to the first post and you guys let me know what you think:
"If you are going to post a kitchen in this thread, please be kind enough to give your opinions on it (likes, dislikes, hard to use, buggy, best kitchen ever... well, you know what I mean). This way, new coming chefs will not have to go through the pain of trial and error"
Click to expand...
Click to collapse
No worries ... let me know once you decide on the format for this thread. Have a look at this thread; might give you some ideas of what could be done for this:
Sous-Chef's Kitchen Utensils & Appliances Review
http://forum.xda-developers.com/showthread.php?t=651026
I use Visual Kitchen
I chose visual kitchen because that was what Da_G used and started me out on. Here are my thoughts:
_________PRO_________
- GUI interface to visually select/deselect packages
- Expandable with Programmable Extra Buttons to ease sorting and cooking stuff
- Allows users to select multiple builds, Lanuages, packages, etc using drop down boxes
- Save/Load configurations and settings
- Robust, Organized and Complete
_________CON_________
- File structure has to be intact or it will fail
- Have to know the building procedure to make sure custom files aren't overwritten
- Packages are in folders, so finding a specific file can be tedious
- Can be overwhelming and confusing to get it setup initially from scratch
I would recommend using this kitchen as it pretty nice. Now of course I say that without using any other kitchen to compare it to... but it does everything I need thus no need to look elsewhere.
_________TIPS_________
EXT folder = Packages (Games/HTC Apps/HTC Dialer/Etc). Additional apps outside of stock MS stuff
OEM folder = Phone specific stuff, OEM customizations, tweaks (usually left alone)
ROM folder = Basic building blocks for WM builds. Has basic device and WM drivers (MSXipKernel updated when SYS gets updated)
SYS folder = WM Build. Contains all the stuff that is stock MS products (updated to change to newer builds)
- Starting out as a new chef... I would suggest that you find a Fully working kitchen designed for your device that is fairly new and updated. Once you can create a working rom, you can then slowly start to expand it by adding more packages and features.
- Don't add too much at once. If you do, and it fails... you'll have to troubleshoot what you added and that can be tedious. It helps to add new packages in groups of 5... so you can test specific parts of the rom before continuing. You'll be surprised that 1 screwed up file can keep your kitchen from completing the building process. Keep that in mind.
- The "EXT" folder is optional and gets updated the most. OEM, ROM, and SYS folders are the only folders really required. Knowing this can allow you to build a very very basic stock Windows build designed for your device. If you have any problems building or flashing, try disabling all of the packages in the EXT folder. If your very very very basic rom still doesn't work... then your "base" kitchen is screwed up. This can be harder to fix.
- Make frequent backups of your "Base" kitchen in the event you screwed something up. I usually will remove the EXT folder and ZIP up the rest in an archive on a memory stick. I update my backup archives after a successful upgrade/edit/tweak of the "base".
player911 said:
I use Visual Kitchen
I chose visual kitchen because that was what Da_G used and started me out on. Here are my thoughts:
Click to expand...
Click to collapse
Updated post #2. Thanks player911!
Hi man!
I think you could add vistang's multidevice kitchen too :
http://forum.xda-developers.com/showthread.php?t=573778
I'm not the right person for a review, but I'm sure one of the guys who used it will be up to the task
Best Regards!
Hi, if you check the link in my signature (Polaris chef corner) you will find quite a few polaris specific kitchens
cruiserrr said:
Hi, if you check the link in my signature (Polaris chef corner) you will find quite a few polaris specific kitchens
Click to expand...
Click to collapse
Thanks cruiserrr for the links. I updated the first post.
Can you give us some insights (in the format in the first page) of pros/cons for some of these kitchens? I don't have a Polaris, so I cannot write any comments about them. Thanks.
i dont have the link but there is a Superjust kitchen for sooo much devices in the net...
+ Que PPC said:
i dont have the link but there is a Superjust kitchen for sooo much devices in the net...
Click to expand...
Click to collapse
Is that the name of the kitchen?
egzthunder1 said:
Is that the name of the kitchen?
Click to expand...
Click to collapse
Here is the link : ivanmmj's SuperJustKitchen
(Supported devices : Artemis , Elfin , Herald , Hermes , Opal)
Regards!
kokotas said:
Here is the link : ivanmmj's SuperJustKitchen
(Supported devices : Artemis , Elfin , Herald , Hermes , Opal)
Regards!
Click to expand...
Click to collapse
Thanks for the link. I will update the first post. Any pros/cons opinions about this?
egzthunder1 said:
Thanks for the link. I will update the first post. Any pros/cons opinions about this?
Click to expand...
Click to collapse
Well it is a kitchen based on OsKitchen by OndraSter&airxtreme!
ps:check post #10 too
egzthunder1 said:
Thanks cruiserrr for the links. I updated the first post.
Can you give us some insights (in the format in the first page) of pros/cons for some of these kitchens? I don't have a Polaris, so I cannot write any comments about them. Thanks.
Click to expand...
Click to collapse
Well, I am not a seasoned cooker but I have updated the polaris chef corner 1st post with my view of each kitchen. Please feel free to take the text if you find it interesting. Most of polaris kitchen's are 26016 EVK kitchens with old kernel, I guess based on gullum's kitchen the first one the share the polaris kitchen for wm6.5. Most of them are based on mega packages. There is one from amenatis based on leo packages but is not 100% completed in english since it is a french kitchen (however, is the one I used as the basis).
For the rest, there are a few other kitchens like vistangs but it seems ondraster kitchen is growing each day. The best one for me is TomAngel's Ondraster kitchen: like any Ondraster's kitchen it has an easy set up of splashscreen and this kinds of things and allows you to cook in several languages at a time. It also has a nice documentation of packages. Additionally TomAngel included a 6.5 native kernel that we are currently testing a few cookers in Polaris but that seems to work and my end with our recmodding hobby.
I personally like better EVK UI but I must say ondraster is also a good solution (and I have "stolen" the kernel from there). I would be glad to share my kitchen I use my own method of cooking shortcuts and tweaks with cmd and mortscript scripts both in the ppc and the pc, so my packages have no app.dat and no png and very few reg files.
cruiserrr said:
Well, I am not a seasoned cooker but I have updated the polaris chef corner 1st post with my view of each kitchen. Please feel free to take the text if you find it interesting. Most of polaris kitchen's are 26016 EVK kitchens with old kernel, I guess based on gullum's kitchen the first one the share the polaris kitchen for wm6.5. Most of them are based on mega packages. There is one from amenatis based on leo packages but is not 100% completed in english since it is a french kitchen (however, is the one I used as the basis).
For the rest, there are a few other kitchens like vistangs but it seems ondraster kitchen is growing each day. The best one for me is TomAngel's Ondraster kitchen: like any Ondraster's kitchen it has an easy set up of splashscreen and this kinds of things and allows you to cook in several languages at a time. It also has a nice documentation of packages. Additionally TomAngel included a 6.5 native kernel that we are currently testing a few cookers in Polaris but that seems to work and my end with our recmodding hobby.
I personally like better EVK UI but I must say ondraster is also a good solution (and I have "stolen" the kernel from there). I would be glad to share my kitchen I use my own method of cooking shortcuts and tweaks with cmd and mortscript scripts both in the ppc and the pc, so my packages have no app.dat and no png and very few reg files.
Click to expand...
Click to collapse
I am putting your review with the others (not that it follows the format that I want, but it is good enough for me )
egzthunder1 said:
I am putting your review with the others (not that it follows the format that I want, but it is good enough for me )
Click to expand...
Click to collapse
Hi, I think it is interesting to share: I can confirm that cooking for Polaris with the kernel shared by TomAngel requires not any recmodding at all !!!
http://forum.xda-developers.com/showpost.php?p=6135182&postcount=27
Do not know if it works for other devices with old kernel, To try import in your kitchen and tell the machine is true kernel
Hi guys, after the release of the latest cedemish tgtool, we may expect that we have the enought elements to create a kitchen for the TG-01. So... let's start:
I built a package with all the tools needed for a custom ROM on the TG-01.
http://www.megaupload.com/?d=DQOSCQBJ
This package contains the latest release of the TGTool created by cedemish and a custom version of ImgfsFromDump that allows ROM sizes up to 512MB.
The package description is:
-TGTool 1.3.19
-OSNBTOOL 1.59
-IMGFS Tools (Custom version up to 512Mb)
-Package Tools
-Xidump beta
That's all you need to create custom roms on your tg01. The knowledge is not included
(29/03/2010) Update: Added bat files to dump and repack tsw files from and to dump directory.
NOTE: The TGTool Thread is: http://forum.xda-developers.com/showthread.php?t=650075 I'm sure you may think to donate to cedemish that released the tool in order to support his work because the tool stills under develop and without cedemish we couln't start this project.
NOTE2: The TGTool 1.3.19 stills not tested as stable and reliable, so the users flashing a ROM created with this tools may brick their device. We will delete this advice once cedemish can asure it's not goint to brick any device
Unpacking a TSW File:
Code:
tgtool -sp *.tsw tg01.os.nb.payload
osnbtool -d tg01.os.nb.payload 2 imgfs.bin
imgfstodump imgfs.bin
Optional:
xidump -x tg01.os.nb.payload
You can also use the runtime to dump with: "tswtodump *.tsw" or droping a tsw file to the bat file in a file explorer window.
Repacking a TSW File:
Code:
imgfsfromdump imgfs.bin imgfs-new.bin
osnbtool -c tg01.os.nb.payload 2 imgfs-new.bin
tgtool -mp tg01.os.nb.payload.New source.tsw destination.tsw
You can also use the runtime to dump with: "dumptotsw source.tsw" or droping a tsw file to the bat file in a file explorer window (the dropped tsw will be the source, a tg01-release.tsw will be created).
reserved 2
reserved 3
sweet....
HOTFILE mirror http://hotfile.com/dl/34607196/21b9adb/tgtool_set.zip.html
Once I've tested the ROM I'm working on, I'll post that as a set of packages.
I've written a set of batch scripts as well if they'd be useful.
Will upload stuff tomorrow, as I need my sleep....
l3v5y said:
Once I've tested the ROM I'm working on, I'll post that as a set of packages.
I've written a set of batch scripts as well if they'd be useful.
Will upload stuff tomorrow, as I need my sleep....
Click to expand...
Click to collapse
That would be nice. Now I'm using this steps to get from the TSW to the dump folder:
tgtool -sp tg01.tsw tg01.os.payload
osnbtool -d tg01.os.payload 2 imgfs.bin
imgfstodump imgfs.bin
Seems to be the fastest way to go.
arag0n85 said:
That would be nice. Now I'm using this steps to get from the TSW to the dump folder:
tgtool -sp tg01.tsw tg01.os.payload
osnbtool -d tg01.os.payload 2 imgfs.bin
imgfstodump imgfs.bin
Seems to be the fastest way to go.
Click to expand...
Click to collapse
I've got that, followed by some of bepes tools, for making a PRB folder layout, and then rebuilding it with PRB. Seems to have booted, with 23549!
Will upload that tomorrow!
Cedesmith is amazing!
l3v5y said:
I've got that, followed by some of bepes tools, for making a PRB folder layout, and then rebuilding it with PRB. Seems to have booted, with 23549!
Will upload that tomorrow!
Cedesmith is amazing!
Click to expand...
Click to collapse
Yes I know how do you build back from the PRB? I couldn't with imgfsfromdump or xidump.
l3v5y said:
I've got that, followed by some of bepes tools, for making a PRB folder layout, and then rebuilding it with PRB. Seems to have booted, with 23549!
Will upload that tomorrow!
Cedesmith is amazing!
Click to expand...
Click to collapse
Crazy stuff man!
First WM6.5.5 Rom on the TG01.
Damn cedesmith is a real genius in software development...this guy is totally crazy. So it seems his tool works just like a charm. Great...
And it's also great that you sucessfully booted WM6.5.5 I3v5y! That's a Milestone in the development.
I'm looking forward to flash the WM6.5.5 Rom tomorow on my TG01 right after you upload it
Best regards and again, I want to thank all the people that worked on the project!
Just one thing i'd like to know...
Is it difficult for us, french users (or more generaly speaking, non english users) to have your rom in French? A lot of modifications to do, or just 2/3 things?
Will we to wait for a french developper, or are you going to make one in french, or something to adapt your rom?
Thanks!
All the people who work on this project are amazing, and you are doing a fantastic work!
That's unbelievable . Actually i can't wait
are you serious?! tomorrow is the dat we all have been waiting for?
too god to be true... I won't be able to sleep tonight
welldone!!!
arag0n85 said:
Yes I know how do you build back from the PRB? I couldn't with imgfsfromdump or xidump.
Click to expand...
Click to collapse
PRB just generates a dump from OEM\XIP\SYS (and relocates the modules). From there, you get an XIP and a dump, and I used IMGFSFromDump (a slightly modified one, but still). The XIP can then be put in to the OS.nb.payload file, and it's done!
One thing that needs to be done is clearing up the mess that is Toshibas OEMDrivers. HTC have put most things in seperate packages which is great, but Toshiba have seemingly failed to do this.
I'll post some batch scripts when I get home.
To try and keep things a little more organised, I'll reply to this here:
Well, I detected some rubish files that may help us to improve the ROM space abalible, and might help also with RAM usage:
Orange UK 10Mb Help Video
Arround ~12Mb from toshibas keyboard
Arround ~15Mb from Toshibas strip menu
Arround ~6Mb from random useless files.
There is also other work arrounds not including myphone, windows live, messenger, marketplace... well... almost any program that usually comes by default to strip down the rom size another couple of MB. I guess we can expect reduction sizes from 40Mb up to 80Mb.
Click to expand...
Click to collapse
The 10MB help video is junk, along with things like the Orange home screen, but unless they're loaded (like the keyboard) there's no RAM usage.
I've built a ROM based on a light WM6.5.5 kitchen I have, so the SYS is pretty clean, but I need to clear up the OEMDrivers etc.
PRB/WMReloc/something else is an absolute requirement to get a booting ROM, otherwise you end up with bad things happening in virtual memory causing a lot of issues.
There is a version of WMReloc that can handle the 6.5 kernel and added slots, or PRB can, but G'Reloc can't (I think). I'm also working on a relocate function, but that could take some time!
Great work l3v5y .I can't wait to flash your rom.
Is there a chance to have it in italian too?
When you will release it please post a videotutorial for flash with shorten pin method.I didn't understand yet what we need to do and how make the bridge between pins.
Alucard24 said:
Is there a chance to have it in italian too?
Click to expand...
Click to collapse
And polish of course
l3v5y great work! Thanks!
will you cooks be using the new radio from the tosh update as it seems to have improved sound a bit or try some different ones to test results.
and if a sense based rom is made am i right in assuming that it probably wouldnt have the same bugs as the port in ather thread.
good work all cant wait to make my tg01 better
about t01a
I have a japanese version known as t01a, Can I test your rom i3v5y?
waiting....
bird_9527 said:
I have a japanese version known as t01a, Can I test your rom i3v5y?
waiting....
Click to expand...
Click to collapse
no way now
complete noob (at cooking)
followed various guides/how-to's etc to set up ervius kitchen with a view to cooking my own roms. Just to check, took a stock rom into the kitchen and then rebuilt it back into an nbh file, there is now about a 40Mb difference between the two files so now I'm not game to say I've done things right. looked through the forum for answers and the only one i can find that might explain this is maybe the new nbh file is optimised. Is this safe to assume? how can I test the rom without bricking my leo?
happened to me the same thing and I gave up Like you, I want to dump a official rom to add some programs and customization but everytime the generated image file (.nbh) was smaller than before. Flashing it left my phone without sense and all programs that came by default with official rom, not mention about those I added myself.
its normal
official roms are not compressed, built roms are compressed, hence the size difference
It seems a little confusing to begin with, this ROM Cooking. But it gets better as you struggle through it. I use the OsKitchen and have cooked sys 23659 successfully. Go ahead and give it a try. I can help you with what little I know.
what i really don't understand is how u port to 23569... been reading for a while... too much info man..
Depends on the Kitchen you use. I use OsKitchen of Airxtreme and it works for me! Once you decide the Kitchen you want to use, then it becomes less tedious. Only one path to follow and learn.
smaiitm said:
Depends on the Kitchen you use. I use OsKitchen of Airxtreme and it works for me! Once you decide the Kitchen you want to use, then it becomes less tedious. Only one path to follow and learn.
Click to expand...
Click to collapse
yeh OsKitchen from Airxtreme... just read your post on that thread..haha great! See that u first tried out 6.5... then 6.5.5.. which base did u use??? 2.13 TMO ROM???
Yes sir. That was what I used. A lot of packages were from Chucky's kitchen. Some were converted to Ext's. Like I said, I am no expert, but things seem to be working fine till now. No major battery drain either. So i guess i have been lucky so far!
Hi pals
I Cooked a WM6.1 19971 Official ROM for OPAL in Ervius Visual Kitchen. The cooked ROM seems quite alright except that:
1.The original ROM was about 100MB while despite the fact that I added a lot of packages, the cooked ROM is about 80MB.
2.None of my packages exist in the cooked ROM when I flash it.
Can you tell me what the problem is?
The smaller size is fine.
What do you mean packages not there?
Are the files not in the windows folder or are you just missing shortcuts?
mnvoh said:
2.None of my packages exist in the cooked ROM when I flash it.
Can you tell me what the problem is?
Click to expand...
Click to collapse
What?!...EVK generates a build_log...look at this, and u'll see, what's in your rom.
Cannot belive that u've applied packages in EVK they wouldn't cook in....strange.
It is happened to me too in the beginning when i was cooking for kaiser and tried to cook inside HTC Mega packages with Manila 2d...i solved it using OsKitchen,lol.
af974 said:
.i solved it using OsKitchen,lol.
Click to expand...
Click to collapse
Sorry...but usin' OSKitchen is still hard work in my opinion. Maybe others think similar to me, and please forgive me @airxtreme!
But still the best kitchen in my opinion is EVK....
Its not true,
OsKitchen compared to any other Kitchen is much more easy to use expecially for newbie users.
EVK it is much complete.
Which is the best between one and another its only a personal taste.
icke said:
Sorry...but usin' OSKitchen is still hard work in my opinion. Maybe others think similar to me, and please forgive me @airxtreme!
But still the best kitchen in my opinion is EVK....
Click to expand...
Click to collapse
Kitchen
I can`t understand that someone say the os kitchen is to difficult
I work with these kitchen hours and days and no problems whatsoever and easys`t do use, if someone got problem to use this kitchen,live the finger from cooking
af974 said:
Which is the best between one and another its only a personal taste.
Click to expand...
Click to collapse
And that's what i said!
For new's, maybe OSKitchen is easier to use...but still beta.
Speak is free and give opinions too...but please people dont start flaming about kitchens.
I mean about what in red....its not nice.
lumisab said:
I can`t understand that someone say the os kitchen is to difficult
I work with these kitchen hours and days and no problems whatsoever and easys`t do use, if someone got problem to use this kitchen,live the finger from cooking
Click to expand...
Click to collapse
While EVK was building the ROM I checked the log it was generating. I saw all my packages. But when I used osKitchen it had problems with the *.dsm file in the packages and said that it's corrupt. I think it's the problem but I used package-creator-v2.7 to convert *.cab files to a package. So obviously the problem is with the package creator.
But on thing that's for sure is that newbies (like me) should stick to osKitchen.
FYI, Barin's OSBuilder has a .dsm autocorrection option.
Well, OsKitchen has its own package creator so all you need is to import your original rom and convert all your cabs again plus it has an auto mui converter,thats mean if that you have some 0410 mui's and you are cooking for 0409 oskitchen wiil rename all the mui for you.It worth a try.
mnvoh said:
While EVK was building the ROM I checked the log it was generating. I saw all my packages. But when I used osKitchen it had problems with the *.dsm file in the packages and said that it's corrupt. I think it's the problem but I used package-creator-v2.7 to convert *.cab files to a package. So obviously the problem is with the package creator.
But on thing that's for sure is that newbies (like me) should stick to osKitchen.
Click to expand...
Click to collapse
Let's state this once for all: Ervius kitchen is basically a GUI to create _skip files that launches a giant batch file that does all the cooking and that needs to be customized for every device: if you created your own _skip files by hand and used a batch file to cook there would be virtually no difference. OsKitchen has a simple GUI by design but that doesn't mean that it isn't orders of magnitude more complete and advanced than ervius kitchen: it does everything from detecting all device/ROM informations without asking anything (the list of supported devices actually has nothing associated to them but the alternative names: no customized fixed, no customized settings, nothing) to cooking with all sorts of checks to prevent bricking or unbootable ROMs and even parsing all the files in the package: if I had proper relocation code (that I was waiting Da_G to write since he knows that stuff better than everybody else) the kitchen could already natively cook its own ROMs. I'm already using all the code I wrote to replace platformrebuilder to implement all sorts of cool stuff like complete validation of all package files and installing packages directly on the phone trough activesync (to avoid having to reflash any time you want to test something) as you can see on the alphas thread, things that on ervius kitchen, where cooking just means running a giant batch file, you could only dream of.
I hope that finally clears the minds of the people saying that ervius is more advanced or complete: it's not, it's just a simple batch file-based kitchen with an unnecessarily complex GUI. It may have some bundled tools that oskitchen doesn't include (like xipporterex, that while works on some NK.EXE wreaks havoc on unofficial native kernel and latest kernels) but having a dedicated button to launch a tool doesn't make a kitchen "more advanced" or "more complete".
No offence and I do appreciate and use your work, but aren't all kitchens just fancy GUI's around a set of batch files and same old imgfstools and platformrebuilder from yesteryear?
pkoper said:
No offence and I do appreciate and use your work, but aren't all kitchens just fancy GUI's around a set of batch files and same old imgfstools and platformrebuilder from yesteryear?
Click to expand...
Click to collapse
Not really, I process all the files before feeding them to platformrebuilder hence the recmod/upx/tweaks/ordering/manila compression/etc without touching any of the original files. I also only use the newest tools available like libnb and osnbtool that the kitchen calls directly and checks the output to warn of any error and to get informations about the ROM format indeed it can import any proper BIN/NB/NBH file and cook it without even knowing what device they come from. The only original imgfstools I keep are nbmerge and nbsplit because I was waiting Da_G to finish his BuildNB function but osnbtool can probably replace both (nbsplit for sure with the -sp parameter).
@OP, it sounds like your package structure is wrong. Are the packages in EXT format (not OEM)? If they're in oem format, none of the files will be included. Just make the packages manually, it's a lot easier.
Can you please post the build log file?
pkoper said:
No offence and I do appreciate and use your work, but aren't all kitchens just fancy GUI's around a set of batch files and same old imgfstools and platformrebuilder from yesteryear?
Click to expand...
Click to collapse
My kitchen (OSbuilder) uses it's own engine to process packages, build dsms, rebase modules, merge dsm and build ROM file. The only external tool i use is "TurboImgfs" by airxtreme.
Yes , when i wrote that EVK ,maybe, its more complete then OsKitchen i was referring to this, only some tools.
airxtreme said:
It may have some bundled tools that oskitchen doesn't include
Click to expand...
Click to collapse
airxtreme said:
Let's state this once for all: Ervius kitchen is basically a GUI to create _skip files that launches a giant batch file that does all the cooking and that needs to be customized for every device: if you created your own _skip files by hand and used a batch file to cook there would be virtually no difference. OsKitchen has a simple GUI by design but that doesn't mean that it isn't orders of magnitude more complete and advanced than ervius kitchen: it does everything from detecting all device/ROM informations without asking anything (the list of supported devices actually has nothing associated to them but the alternative names: no customized fixed, no customized settings, nothing) to cooking with all sorts of checks to prevent bricking or unbootable ROMs and even parsing all the files in the package: if I had proper relocation code (that I was waiting Da_G to write since he knows that stuff better than everybody else) the kitchen could already natively cook its own ROMs. I'm already using all the code I wrote to replace platformrebuilder to implement all sorts of cool stuff like complete validation of all package files and installing packages directly on the phone trough activesync (to avoid having to reflash any time you want to test something) as you can see on the alphas thread, things that on ervius kitchen, where cooking just means running a giant batch file, you could only dream of.
I hope that finally clears the minds of the people saying that ervius is more advanced or complete: it's not, it's just a simple batch file-based kitchen with an unnecessarily complex GUI. It may have some bundled tools that oskitchen doesn't include (like xipporterex, that while works on some NK.EXE wreaks havoc on unofficial native kernel and latest kernels) but having a dedicated button to launch a tool doesn't make a kitchen "more advanced" or "more complete".
Click to expand...
Click to collapse
Don't let them get you down man. Ervius's kitchen is a piece of **** in my opinion. The GUI blows and it crashes on the smallest thing that's not exactly right with a package. Did I mention the GUI is horrible ?
I will say it as well, erv's kitchen is NOTHING but a glorified GUI for platformrebuilder which is the real workhorse.
p.s. I made my own kitchen GUI, based on platformrebuilder as well. Mine's designed to cook for 12 devices at a time though... so I can't exactly share it. PM me if you'd like the details necesssary to make Samsung Omnia 2 ROMs with prb though, it seems nobody else seems to know what the "secret" is... I just think they didn't try hard enough. lol If anything, you can add 4 more devices to your already impressive collection of supported devices