as the title implies i am unsuccessful at building the rom with da_g's kitchen, iv made shure iv place the sys and oem were they go, same with my ext's. I even ported the xip.bin witch it is int necessary since da_g post hes new build's with that already done, and even when doing that the rom fails to build, any help would be appreciated, iv attached my build log see if you guys see what im doing wrong.
regards
siulmagic
Remove the sys package SQM; you don't need it (or want it) with dummycustsat included. It's just the error reporting crap for MS.
hmm i deleted them but the rom stil does not build
You need one or the other. Do you have the correct oem stuff for a kaiser?
Also, if you're doing a Kaiser rom, make sure that the real 6.5 aku box is unchecked, and you probably need to recmod a ton of modules. That may be your main problem. You're cooking in pretty much all of the sys folders, and they're filled with modules. I believe that browsingie and bronzeres are two of the packages that people using 6.1 kernels recmod to get a free slot 0.
oh my bad lol i forgot to change my sig i do not own a kaiser anymore, iv got a htc raphael now thats y im posting here XD
Well, my guess is that it's the sqm problem. Note, there's a reason that the mods package is called "DummyCustsat-DisableSQMFirst". You need one or the other. One or the other. Not both or neither. Use dummycustsat.
You should also use the older comm manager. The newer one is buggy as hell (especially in landscape). Don't you need one of the XT9 packages? I'm pretty sure there are major dependencies in there that are needed by a lot of processes (that's where the et9...dll's are, isn't it?).
I'm also not sure what's going on here:
Package: ShareDLL_2.0.070522.0000 Included Into ROM!
ERROR!!! Found File duplicate on Module...
Package: SharedModules_1_01_19142727_00 Included Into ROM!
Click to expand...
Click to collapse
I have sharedll cooked into my builds, but not sharedmodules. It sounds like they're interfering with one another.
hmm i already deleted the sqm oem package so the one left and the ones thats enabled is the dummy one, but it still fails to build
Farmer Ted said:
Well, my guess is that it's the sqm problem. Note, there's a reason that the mods package is called "DummyCustsat-DisableSQMFirst". You need one or the other. One or the other. Not both or neither. Use dummycustsat.
You should also use the older comm manager. The newer one is buggy as hell (especially in landscape). Don't you need one of the XT9 packages? I'm pretty sure there are major dependencies in there that are needed by a lot of processes (that's where the et9...dll's are, isn't it?).
I'm also not sure what's going on here:
I have sharedll cooked into my builds, but not sharedmodules. It sounds like they're interfering with one another.
Click to expand...
Click to collapse
hey i yust fixed the module conflict but it stil wont build, could it be the nk.exe the one i got is from the kitchen da_g posted a long time ago
He posted a newer one in the 6.5 thread (not sure the link is up, though). That's the one you want to use, it's much better than the older one in his full kitchens.
You should try to just cook one of his preconfigured roms and see if it builds properly. Otherwise, you may have a problem in there that's hard to track down.
Farmer Ted said:
He posted a newer one in the 6.5 thread (not sure the link is up, though). That's the one you want to use, it's much better than the older one in his full kitchens.
You should try to just cook one of his preconfigured roms and see if it builds properly. Otherwise, you may have a problem in there that's hard to track down.
Click to expand...
Click to collapse
i would if the links were up thy removed them do to the takedown notice by microsoft, and yes preconfigured roms build just fine only mine is funky and it doesn't build
siulmagic said:
i would if the links were up thy removed them do to the takedown notice by microsoft, and yes preconfigured roms build just fine only mine is funky and it doesn't build
Click to expand...
Click to collapse
Just use one of the pre-configs as a base for your rom. Add a package or two at a time and build (you don't need to flash). See if you can isolate the problem that way.
Now that I think of it, I did have a problem last week doing a build, and it was the first time I've ever had VK crash on me. I use a zip file to install all my apps into \program files. Anyway, I was editting the file; I unzipped it into the files directory of the package, made some changes, and then re-zipped it. But I forgot to delete the actual folder after doing the re-zip. It caused the kitchen to crash. It's possible that you have a stray folder in one of your packages. I've also read that if you get a stray file in a module folder, it can cause the build to fail. So, add things one at a time, and figure out which package is corrupted. Then fix it.
Farmer Ted said:
Just use one of the pre-configs as a base for your rom. Add a package or two at a time and build (you don't need to flash). See if you can isolate the problem that way.
Now that I think of it, I did have a problem last week doing a build, and it was the first time I've ever had VK crash on me. I use a zip file to install all my apps into \program files. Anyway, I was editting the file; I unzipped it into the files directory of the package, made some changes, and then re-zipped it. But I forgot to delete the actual folder after doing the re-zip. It caused the kitchen to crash. It's possible that you have a stray folder in one of your packages. I've also read that if you get a stray file in a module folder, it can cause the build to fail. So, add things one at a time, and figure out which package is corrupted. Then fix it.
Click to expand...
Click to collapse
i found the problem omg i feel stupid, the problem was i named my sys forlder 23071 and then the xip and ext folders 23070, all i had to do was rename sys to 23070 and bam build successfully
siulmagic said:
i found the problem omg i feel stupid, the problem was i named my sys forlder 23071 and then the xip and ext folders 23070, all i had to do was rename sys to 23070 and bam build successfully
Click to expand...
Click to collapse
You should rename them 23081 and step up to a real build.
again i was goin to download that build but due to the takedown notice that build is gone from xdaXD
meh now i cooked the rom fine then i flashed it and it wont boot goh
im prety shure i need the latest nk.exe, the one that has the native kernel, this one i have im shure its the old one tha tneeds rec moding
Related
Hey Guys,
Yet another sleeples night, looking at something that is probably simple and getting no where.
THE PROBLEM:
APPARENTLY you can change a CAB file into an OEM so that it can be used in Pandora Kitchen, the kitchen thread says its possible, but doesnt really give directions as to how.
Considering this is a new thing to, and there is no info about this on the site (that i can find)
Can someone please tell me step by step how to do this, and by step by step i mean:
1).................
2).................
3).................
4).................
etc etc
Thankyou for your help in advance
Here is a test package I made, but I keep getting a registry errors. Maybe someone can tell me what im doing wrong. I think it was better to keep all this in the kitchen thread personalley but as long as I can figure this out I dont really care.
Extract this file and take the "Remote Desktop" dir and drop it in the OEM dir in the Kitchen, and it shows up and all but when you go to build with teh green arrow I get a registry compiling error.
I also attached the original cab file that I started with when attempting to create this package.
Also attached is the cab manager that Matt uploaded, I am sure its the same as the one posted above but this has a readme and what not.
First Matt told me this:
Using this tool (many out there, this one's free and does a good job), extract the cab to a folder, then click on XML and grab the .rgu contents. Be wary of the format, as you have to delete any spaces between entries, such as "biteme" = dword : 00000001 should read "biteme"=dword:00000001.
Also, ensure that any path in this file (file system, not registry) is in this format: "\\Windows\\Startup" The second slash is required. Also, remove any references like %ce%\Windows, just change it to "\\Windows". You'll get the idea. If it ain't right, BuildOS will fail while creating the registry.
Move all the files into the top level in the folder you made, and remove all the extra crap like the inf file, and sometimes there's an xml file there too - note that you may need to convert to a provxml if the settings in it are required.
Use this site http://www.famkruithof.net/uuid/uuidgen (verion 4) to get a new GUID. I'd suggest coping a .rgu and options.xml file from another package since the file has to originate a certain way - and only use notepad to edit.
Just follow the example in the other packages - you'll find just about every way to do things in there.
As far as more details on using the program, just play with it. It's pretty simple
Then Bennec83 told me this:
what exactly are you trying to do? extract a CAB? if you are, using the file i uploaded earlier:
1)Launch CAB Manager.exe
2)on main screen extract CAB to a folder
3)click on the XML tab in top bar of the main window of CAB Manager.exe
4)in the window that opens, select Registry Keys
5)copy everything from the screen into WORDPAD
6)remove all the spaces
7)save the file as "UNICODE", once saved change the extension to somename.rgu
if you are trying to add an OEM to this kitchen i dont think you can just add them, please correct me if im wrong.
i hope this helps, if not tel me abit more about wat u want to do n ill try to help abit more!!
I understand the INF file as well, I just dont know how to add multiple directories as the destinations for a package, when a cab inf will tell you where there all suppost to go.
--Update--
I removed the NON-WORKING package, as it is now obsolete, see post below I got it working.
Ok then I understand the logic, and then the proper elaborated instructions can be pasted at the first or second topic of the Kitchen thread.
So I guess im doing something wrong with the reg, I have tried it a bunch of diffrent ways by comparing it to existing packages but I still cant seem to get it.
This quote by matt is what leads me to believe that.
Also, ensure that any path in this file (file system, not registry) is in this format: "\\Windows\\Startup" The second slash is required. Also, remove any references like %ce%\Windows, just change it to "\\Windows". You'll get the idea. If it ain't right, BuildOS will fail while creating the registry.
Ok I did it, I was reading an old post of bepe's and he said "add the reg to the end of the file (and the last line must be empty)" and so I hit enter and left the last line blank and BAM it worked so here is my first package contribution.
Maybe you can start adding these to the first post and we can start to make a collection for matt to add and test with his kitchen ?
Here is another one HTCustom 1.7 ready to go package for the kitchen
Damned if I can work it out!
Can anyone please package any of the following cabs?
Ive added JUVS HTC Home because the one included in the kitchen has the coloured icons not the original b&w.
Many many thanks in advance
I am still not able to completly figure out how to make a package where you must put files in diffrent locations other then the windows folder ? I would veyr much like to figure this part out.
I dont think he's having a go at you - he's just as frustrated as you and I with this. I would love to be cooking my own roms and with the wonderful pandoras kitchen I am getting alot further along but I guess I got a lot further to go!
well, by searching you can find how to do this!!!
click on this ftp://xda:[email protected]/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf
this pdf file got what you need!!
under "Making a Package from a CAB file"
Look here bennec83, the comment i made was not meant to be a flame at all. If anything, it should have helped you alot with what you were trying to accomplish with the program and, making packages. I mean how much more direct can i be with helping you? As I said to you before, yes some of the chef can be a little vague with explaining the "How To's" of cooking or anything else, but that still didnt stop my progression of learning what i wanted to learn on here. What i explained in the CORE's Kitchen thread, was basically 80% self taught thru reading post & threads on xda, google searching, and trial and error. The other 20% was thru xda forum members input. I have a basic understainding of computers with no type of programming skills, and yet still, i was able to grasp the concept of cooking roms and making packages. Yes sometimes you have to put 2 and 2 together to figure things out on here. How I did it was I looked inside CORE's additional OEM packages and noticed that the files inside all the oem were extracted into the root of the folder's Dir...ok..so I would assume that you spent considerable amount of time trying to figure out that OEM package program(inside CORE's Kitchen its called Cab Analizer), then i would assume that you know that it extracts files within a .cab...ok... with that given....if you look back into an already made OEM package and many others, you'll notice that most ,if not all, carry an "initflashfile.txt"(which i figured out the correct data input) and many packages also carry .rgu & dsm files, so guess what....you need to find out what are .rgu & .dsm files, and there functions(if know no ones whats to tell you in a timely manor then, search or google, like i did!) Once you learn about those then, you'll notice that the OEM package program you have infront of give information about the reg keys of the cab (if available), then you start putting 2 & 2 together! You mention in your quotes that the programs sucks ass, well that program is a key part in making packages, If you can find a better one, please let me know!
NightmarE said:
well, by searching you can find how to do this!!!
click on this ftp://xda:[email protected]/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf
this pdf file got what you need!!
under "Making a Package from a CAB file"
Click to expand...
Click to collapse
thankyou so much for this, i actually know what to do now i really appreciate this. you dnt know how much!!!
thanks alot
chrisnash said:
I dont think he's having a go at you - he's just as frustrated as you and I with this. I would love to be cooking my own roms and with the wonderful pandoras kitchen I am getting alot further along but I guess I got a lot further to go!
Click to expand...
Click to collapse
you are right that wasnt flamage!! i have been lookin so long in this forum i totally didnt think the answer would be in the wizard forum.
i have read and understood the instreuctions here:
ftp://ftp.xda-developers.com/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf
i just wish i cud have found it earlier
perhaps I'm an utter fool, but I'd like some clarification from those of you who understand this, mind you I do have Faria's PDF:
1) For a .cab with purely registration files (ie, the Cingular WAP Settings) that contains a .inf when extracted, all I would need is the .rgu to put into BuildOS, right?
2) The .dsm file (and iniflashfiles) are only needed if the .cab is an actual application, and the .dsm file that you create can very well be empty (from what I understand from Faria's rom).
Maybe it's a lack of sleep, but I'm just not getting my head around this and am so far using the Install Cabs feature from HTCustom 1.7 after flashing.
I was trying to do the cignular settings and It seemed to me that all those reg entries appear like blank er something was wrong with them, I could be wrong but thats what it appeared like to me.
Bennec, ok then bro, my mistake, I guess I shouldnt of assumed that post was directed towards me, it just felt that way and I know you were frustrated.
Lets make this the best CAB to OEM Package thread ever and start a collection on the first post, also with all you have learned now, have you figured out a way to make a package with a cab like opera where the files must be placed in to diffrent dirs ?
where are you all stuck at?
to move files to a different directory you need to use initflashes. Keep in mind that this copies it to a different directory not actually moves it. The original file will still be in \\windows
If all you want is to add registry entries, add them to an existing packages registry entries. If you create a new package for the registy entries it should have a dsm file as well.
If you want the check box in buildos you will need to create an option.xml file as well.
bennec83 said:
you are right that wasnt flamage!! i have been lookin so long in this forum i totally didnt think the answer would be in the wizard forum.
i have read and understood the instreuctions here:
ftp://ftp.xda-developers.com/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf
i just wish i cud have found it earlier
Click to expand...
Click to collapse
I'm glad you found the info you need, and are on your way to making progress. I apologize for not being able to assist more than I did, but I've got my hands full getting v3 ready for release.
Good luck and happy packaging!
NYD - long time, no see!
goto the CORE's kitchen thread. Read my posts and familiarize urself with a program called "compare it". Use this program to compare ur registry when the app is freshly installed, to the registry without the app installed, and pull the reg keys that way!
mattk_r said:
I'm glad you found the info you need, and are on your way to making progress. I apologize for not being able to assist more than I did, but I've got my hands full getting v3 ready for release.
Good luck and happy packaging!
NYD - long time, no see!
Click to expand...
Click to collapse
I understand you have lots to do on your kitchen, congrats BTW!! amazing kitchen, how is touch flo goin?
notyourdaddy said:
where are you all stuck at?
to move files to a different directory you need to use initflashes. Keep in mind that this copies it to a different directory not actually moves it. The original file will still be in \\windows
Click to expand...
Click to collapse
Hmmmmmm.
So its not possible to cook a Rom with custom apps in Progam Files only? I mean if they are always in \\windows too then its better to install the files than to cook it in the rom.
I have always believed you should add as little as possible to Rom:
From Tadzio's 'Want more Storage' Thread.
tadzio said:
...clip...
I modified mamaich's ImgfsTools so that they now create the smallest possible OS.nb from a 'dump' directory, and also write the partition table and MSFLSH header matching the new size.
...clip... make a ROM as small as at all possible, removing anything that users may not want, and turn every removed feature into a .cab that users can install to Storage...clip...
Cheers
Daniel
...clip...
Click to expand...
Click to collapse
Over the coming days, I shall be writing more below as a tutorial for ROM cooking/Modification.
First, you will need a ROM kitchen. For ease of use, I would recommend Inteks Neokit which can be found here.
Next you will need a base ROM (any Prophet ROM will do) many can be found here.
Now, load neokit and then select the "Select nb/nbf" option. Select the ROM you want to modify and then click "dump rom". This will deconstruct the ROM and put all the files included in the ROM into a single directory.
If you know the files you want to change (such as images) you can simply find them in the "dump" folder (click on the "..." button on neokits main screen) and replace them with the files you want.
If you want to add a program, you can do it two ways:
Create an OEM Package.
Install a CAB after the flashing of the ROM.
If you want to change the registry, the "default.rgu user.rgu" tab must be selected.
To change shorcuts, you will need to edit the "initflashfiles.dat".
After modifying the ROM, you will need to build it back up so that you can flash it. Go to the main screen and click "build ROM" click yes, and then you will have to wait for this to complete.
Now you need to turn the *.nb files into a *.nbf. Follow the instructions in neokit for this.
This will be updated with more detail when I have the time to do so.
If you have any questions do not hesitate to ask as I and others will be willing to help.
What can be safely removed?
Below are the names of packages that can be removed without causing instabilities. Having said that, the may dramatically reduce the functionality of a ROM. The best way to find out what ca be removed is to try it yourself, flash it and see if anything works/doesn't work and then build on it from there. Post your findings here and help someone else!
Internet Explorer-Related Packages
Browsing--Base for IE
Browsing_DPI_96--Images related to IE
Browsing_Lang_XXX (where XXX is the region code) Can be removed or replaced for localisation.
BROWSINGCORE--This might cause instabilities to the OS as lots of programs rely on these files
Also reserved.
Thanks...
It's really helped...
What files I can remove for more space?
amaleena said:
What files I can remove for more space?
Click to expand...
Click to collapse
This question can't be answered, it is a bit the same as "How do I get to Amsterdam?" Without telling us where you are!
How can anyone tell you what is to be removed in your ROM if we don't know what files are there in the first place? This can be different depending on wich ROM you use; some are allready "cleaned out" while others are stuffed to the max.
But above all, it is up to you to decide what you will sacrifice to create more space. The challengeing part of this game is to try, explore and discover and experience that overwhelming satisfaction when a plan comes through!!
So, my advice: don't bother to refrase your question but just go for it yourself....
rondol1 said:
This question can't be answered, it is a bit the same as "How do I get to Amsterdam?" Without telling us where you are!
How can anyone tell you what is to be removed in your ROM if we don't know what files are there in the first place? This can be different depending on wich ROM you use; some are allready "cleaned out" while others are stuffed to the max.
But above all, it is up to you to decide what you will sacrifice to create more space. The challengeing part of this game is to try, explore and discover and experience that overwhelming satisfaction when a plan comes through!!
So, my advice: don't bother to refrase your question but just go for it yourself....
Click to expand...
Click to collapse
I agree with that, however from personal experience I think a short list of things that can be removed might be helpful...
Is it possible to change only the language of a rom? How can i Do it?
l3v5y said:
I agree with that, however from personal experience I think a short list of things that can be removed might be helpful...
Click to expand...
Click to collapse
That right!.I mean list of files that can be removed safely.Example, If I would like to remove Microsoft word. I should remove file1.exe,file2.dll,...etc.
Sorry for my poor English.
xfounder said:
Is it possible to change only the language of a rom? How can i Do it?
Click to expand...
Click to collapse
You have to overwrite the MUI files, change some paths in the Regsitry (default.hv and user.hv, konvert them first) and change the paths in the initflashfiles.dat! That's all!
l3v5y said:
Over the coming days, I shall be writing more below as a tutorial for ROM cooking/Modification.
First, you will need a ROM kitchen. For ease of use, I would recommend Inteks Neokit which can be found here.
Next you will need a base ROM (any Prophet ROM will do) many can be found here.
Now, load neokit and then select the "Select nb/nbf" option. Select the ROM you want to modify and then click "dump rom". This will deconstruct the ROM and put all the files included in the ROM into a single directory.
If you know the files you want to change (such as images) you can simply find them in the "dump" folder (click on the "..." button on neokits main screen) and replace them with the files you want.
If you want to add a program, you can do it two ways:
Create an OEM Package.
Install a CAB after the flashing of the ROM.
If you want to change the registry, the "default.rgu user.rgu" tab must be selected.
To change shorcuts, you will need to edit the "initflashfiles.dat".
After modifying the ROM, you will need to build it back up so that you can flash it. Go to the main screen and click "build ROM" click yes, and then you will have to wait for this to complete.
Now you need to turn the *.nb files into a *.nbf. Follow the instructions in neokit for this.
This will be updated with more detail when I have the time to do so.
If you have any questions do not hesitate to ask as I and others will be willing to help.
Click to expand...
Click to collapse
From my rom is *.nbh not nb or nbf, what next?
What device is that from?
*.nbh files can be read using this: http://forum.xda-developers.com/showthread.php?t=377514
l3v5y said:
What device is that from?
*.nbh files can be read using this: http://forum.xda-developers.com/showthread.php?t=377514
Click to expand...
Click to collapse
HTC p3600, Trinity
The tools I mention in the first post are designed purely for the HTC Prophet... I have no idea about what to do for a Trinity...
l3v5y said:
Over the coming days, I shall be writing more below as a tutorial for ROM cooking/Modification.
First, you will need a ROM kitchen. For ease of use, I would recommend Inteks Neokit which can be found here.
Next you will need a base ROM (any Prophet ROM will do) many can be found here.
Now, load neokit and then select the "Select nb/nbf" option. Select the ROM you want to modify and then click "dump rom". This will deconstruct the ROM and put all the files included in the ROM into a single directory.
If you know the files you want to change (such as images) you can simply find them in the "dump" folder (click on the "..." button on neokits main screen) and replace them with the files you want.
If you want to add a program, you can do it two ways:
Create an OEM Package.
Install a CAB after the flashing of the ROM.
If you want to change the registry, the "default.rgu user.rgu" tab must be selected.
To change shorcuts, you will need to edit the "initflashfiles.dat".
After modifying the ROM, you will need to build it back up so that you can flash it. Go to the main screen and click "build ROM" click yes, and then you will have to wait for this to complete.
Now you need to turn the *.nb files into a *.nbf. Follow the instructions in neokit for this.
This will be updated with more detail when I have the time to do so.
If you have any questions do not hesitate to ask as I and others will be willing to help.
Click to expand...
Click to collapse
hi l3v5y :Moderator,
I was a new member of xdaDef...
i'd ever cook the rom base on the RK at PDAMobiz.com..
But i got the prob. about how to add the program into the OEM package 'coz some programs i got that contained the old version.
Anyway i used the package creator 5.5 to do create it into the OEM file...
after that i can collect the program in OEM and can build OS but after upping the ROM ....
it;s got HANG.... Oh no..
I tried many many time to change something but i didn't have the knowledge about RM..
could u pls. suggest me by e-mail how to cook the rom by myself after i d/l the SYS, OEM, and XIP of "CE 5.2.19960 (issue form HTC Raphael) ported for ELF"..
I wanna be a rom cooker asap....
Best Regards,
JoeMan
[email protected]
Also another suggestion:
When removing one or more software you should also remove the setting in initflashfiles.dat and the registry in default/user.rgu, that's call clean remove.
When adding softs, also include adding path and registry also.
For better removing or adding soft you should look inside their cab (I use WinCE cab manager)
legedug said:
Also another suggestion:
When removing one or more software you should also remove the setting in initflashfiles.dat and the registry in default/user.rgu, that's call clean remove.
When adding softs, also include adding path and registry also.
For better removing or adding soft you should look inside their cab (I use WinCE cab manager)
Click to expand...
Click to collapse
WOW..... LEGEDUG..... a rom master now....
legedug said:
Also another suggestion:
When removing one or more software you should also remove the setting in initflashfiles.dat and the registry in default/user.rgu, that's call clean remove.
When adding softs, also include adding path and registry also.
For better removing or adding soft you should look inside their cab (I use WinCE cab manager)
Click to expand...
Click to collapse
Thaks for yr suggestion....
But it is my hard understanding..
could u pls. show me the example?
i'll try it...
Regards,
JoeMan
Thank's dioxda2 for teasing me
But I'm a learning by doing,
Still too far away from being a rom master
monjikung said:
Thaks for yr suggestion....
But it is my hard understanding..
could u pls. show me the example?
i'll try it...
Regards,
JoeMan
Click to expand...
Click to collapse
Oke
For instance, you want to add smsbackup in your rom
Open smsbackup.cab with wince cab
There are 2 files (exe and dll), 1 shortcut (lnk) and 4 registry entry
So, you should add 3 files (exe. dll, and lnk) to dump folder (adding fiile from neokit tools from Inteks)
Adding some initflash.dat with some path (where do you want to put the link file)
Adding 4 registry key in default or user.rgu
For removing, the process will be reversing.
Hope this will help you
I think you should try practicing.
So I've spent the better part of the evening getting familiar with cooking ROMs--very cool! I cooked a few using PPCGeeks kitchen and played around with different things/options. I've kind of hit a road block--did some searches but really couldn't find anything solid that would guide me. Hopefully someone can point me in the right direction.
1) In the wiki, there are stock ROMs downloadable for Sprint. Is there any way to get the OEM packages that were used to build the ROM? Reason is that there are a few apps that I would like to have that I have not been able to locate that are in the stock ROM.
2) If I have the CAB for an app, is there an easy way to create an OEM package for it? I picked apart a CAB and it looks like it can be done manually but a couple of the CABs I have are pretty big with a ton of files.
Thanks!
Joe
Hey!
I'd recommend going on to ppckitchen.org and downloading their ppckitchen Kitchen. Once you download the application, run the update (if you're running Vista, you'll want to run that as an admin) which will download several rar files containing OEMs and ROM files. Be patient, they're big.
Once updated, navigate to the Kitchen install directory (mine is in C:\Program Files\PPCkitchen.org\BuildOS) and copy the OEM RAR files from the Kitchens directory to new location. I'd recommend the core, PPCKitchen_OEM, Carrier and Generic files as they contain most of what you'll be looking for.
Now, unrar the files and take the OEMs you want to your usual kitchen file (I use DCD 3.2.6). Be aware that some OEMs will not work with some ROMs and wil crash the BuildOS, so experiment and see what works for you. Also, take a look inside the PPCKitchen app (pay respect to the Master Chef) and see if the OEMs you want don't require prerequisite OEMs to be installed.
Voilá... dinner's served.
Hope this helps.
As for the CAB OEMizing, never done that, I pretty much scavenged everything I need. Maybe someone else can help us both.
drnoir said:
Hey!
I'd recommend going on to ppckitchen.org and downloading their ppckitchen Kitchen. Once you download the application, run the update (if you're running Vista, you'll want to run that as an admin) which will download several rar files containing OEMs and ROM files. Be patient, they're big.
Once updated, navigate to the Kitchen install directory (mine is in C:\Program Files\PPCkitchen.org\BuildOS) and copy the OEM RAR files from the Kitchens directory to new location. I'd recommend the core, PPCKitchen_OEM, Carrier and Generic files as they contain most of what you'll be looking for.
Now, unrar the files and take the OEMs you want to your usual kitchen file (I use DCD 3.2.6). Be aware that some OEMs will not work with some ROMs and wil crash the BuildOS, so experiment and see what works for you. Also, take a look inside the PPCKitchen app (pay respect to the Master Chef) and see if the OEMs you want don't require prerequisite OEMs to be installed.
Voilá... dinner's served.
Hope this helps.
As for the CAB OEMizing, never done that, I pretty much scavenged everything I need. Maybe someone else can help us both.
Click to expand...
Click to collapse
Thanks! I did all that already but I'm in "learning" mode right now so I wanted to try a bunch of different things out... one of which was creating OEM files from cabs.
joestop said:
Thanks! I did all that already but I'm in "learning" mode right now so I wanted to try a bunch of different things out... one of which was creating OEM files from cabs.
Click to expand...
Click to collapse
This is what you need. Its great! Turns CAB's into OEM's. Its what I use in my kitchens and ROMs.
http://forum.ppcgeeks.com/showthread.php?t=9830
Good Luck!
-Scott
scrosler said:
This is what you need. Its great! Turns CAB's into OEM's. Its what I use in my kitchens and ROMs.
http://forum.ppcgeeks.com/showthread.php?t=9830
Good Luck!
-Scott
Click to expand...
Click to collapse
THANK YOU!!!
do you guys happen to know where i could find a cab for the icons on the start menu that you move them by simply tapping and holding on them? thanks
Have a look at the last 50 posts or so in Da_G's 6.5 kitchen thread; I recall seeing something about that functionality working when specific .DLL's are in the ROM.
I'm not sure if it will be possible to install the .DLL's after the fact. Worst case, you may need to post a request in the ROM related thread that you are using if you are not cooking your own ROM's.
HTH,
I saw something also in NRGZ28's mercury rom where you're able to do that
http://forum.xda-developers.com/showthread.php?t=536751
He just updated the rom today with some new features. I'm interested in this as well. Maybe it will work with the iphonetoday today plugin
I couldn't get it to work on any other rom other then several of the later versions. At this point I think it has to even be cooked in because the features come from an updated Shell32.exe
I'd love to be able to keep my 21222 roms and simply just update it for the start menu.
cooking it is the way to go now. I'm using 21928 with the gwes from 23001 so the big dialog boxes are no longer there and I can shift the start menu icons around easily.
But if it's the other way around, using 23XXX build with the shell32 from the 2192X series, the phone doesn't boot...I'm probably doing something wrong because NRG and a couple of others obviously got it to work with the 23XXX builds...
Last thing, if this thread is moved to Development and Hacking, we might get a better response, after all this is a good thing for all phones and not just Raphael.
@lukesky:
An alternative could be someone who compiles as many of the "generic" Tricks & Tips from this thread and the RAPH 6.5 Kitchen thread and creates a new thread in Dev & Hacking.
nudge nudge, wink wink
Try with this shell32. Report back.
CraZyLiLbOy said:
Try with this shell32. Report back.
Click to expand...
Click to collapse
what exactly would one do with this file to see if it does the trick?? drop it in the windows folder?? please explain it thats cool, thank!!
I think we have to cook the shell32.exe in. I tried copy and pasting it into the windows directory, doesn't work. The orig shell32 is still there and doesn't get replaced.
Supposedly you can't just drop it in. I've tried numerous occasions to get the feature to take in the 21222 build and can't get it. I followed the same exact steps with success for 23009.
Perhaps copying the CHome package might help. Something else is new in the later roms that obviously isn't in the older builds. I'll run both builds through BeyondCompare and see what that pulls up.
[EDIT] lol there are so many differences I couldn't narrow it down to anything. I figured as much anyway[/EDIT]
When you put the .exe file in your device, it creates a dll file by itself which is shell32.dll...now drop that dll file in your windows folder and soft reset..Dont replace the shell32.exe with the old one..if you do then your phone will not boot.
CraZyLiLbOy said:
When you put the .exe file in your device, it creates a dll file by itself which is shell32.dll...now drop that dll file in your windows folder and soft reset..Dont replace the shell32.exe with the old one..if you do then your phone will not boot.
Click to expand...
Click to collapse
It worked! But messed up icons in startmenu in my 23017 build. Had to install original startmenu cprs from ROM, then everything was back to normal! Thanks for the tip...
CraZyLiLbOy said:
When you put the .exe file in your device, it creates a dll file by itself which is shell32.dll...now drop that dll file in your windows folder and soft reset..Dont replace the shell32.exe with the old one..if you do then your phone will not boot.
Click to expand...
Click to collapse
Sorry, but Where shell32.DLL should be created? And where exactly .exe file should be placed?
Thanks.
j0kkk3r said:
Sorry, but Where shell32.DLL should be created? And where exactly .exe file should be placed?
Thanks.
Click to expand...
Click to collapse
Place it in your root device.
Which build number is this shell32 from?
This is the kitchen I am currently using to build my rom series, my main reasons for releasing this are to try and progress development of 6.5 builds on the athena.
I am going to assume that if you have in depth knowlege to rom building that you would have probably put your own kitchen together, so please dont post questions etc if you have tried to do something out of your comfort zone i.e porting new builds(this is a bit more involved)
The kitchen contains saved builds of my latest releases, 23060 and 23053, load whichever you wish and add and remove packages etc, I will try and assist as much as I can.
There are many guides on ervius kitchen I would suggest reading them if you are new to it.
My hope is that we can resolve the few remaining issues I have in a more efficient way than me spending 5/6 hours every night building and testing roms, the main existing problems are:
DRM
Manila
Autorotation
All the saved config files have been recmodded to attain max slot 0 memory allocation, I would not advise recmodding any more modules as this will probably cause a non booting rom.
I will try and update with latest versions with a config file as they become available.
Please do not release roms into the forums, my intention is that you use it to learn and build your own spec roms
Download Link!!!!!
http://www.megaupload.com/?d=YI469SR4
***PLEASE NOTE***
THIS IS NOT FOR PEOPLE WHO DO NOT UNDERSTAND WHAT THEY ARE DOING, YOU RUN A HIGHER RISK OF BRICKING YOUR DEVICE IF YOU GO IN BLIND, AS WITH ROMS THIS IS FOR SPL3.5 DEVICES, I AM MORE THAN HAPPY TO ASSIST ANYONE WHO NEEDS IT PROVIDING YOU ACCEPT I CANNOT GIVE ALL MY TIME TO THIS AS I HAVE A FAMILY AND A JOB TO LOOK AFTER, IF YOU NEED HELP I CAN WALK YOU THROUGH IT VIA MSN ETC
******Reserved************
********Reserved*********
Lol, first hurdle, the kitchen is 802mb and sendspace wont allow me to upload more than 300mb
anyone got any ideas
can you upload a torrent?
ZIP > split > upload parts?
Split to 100MB parts and PLEASE upload it to Rapidshare
Thanks
you can rar/zip and split it into 250MB parts (less parts to download than to have each part at 100MB) or you can upload to torrent (but we would need seeders....the dedicated file servers are a better option though)
I managed to reduced the size somewhat and its now on megaupload, the link is now in the first post.
For those wishing a beginers course, I am going to try and do one tomorrow, but will start a seperate post for it.
I have not tested this kitchen but it should work fine.
hey avenger, will you be including the new 23071 build in the kitchen or for additional download? also does the kitchen offer xip and sys porting?
lennie said:
hey avenger, will you be including the new 23071 build in the kitchen or for additional download? also does the kitchen offer xip and sys porting?
Click to expand...
Click to collapse
I will probably build a 23071 rom tonight and see how it looks, then consider releasing it into a kitchen, yes the kitchen offers sys and xip porting, but it needs a couple of things doing to get it to work with the athena kernel
avengerpenguin said:
I will probably build a 23071 rom tonight and see how it looks, then consider releasing it into a kitchen, yes the kitchen offers sys and xip porting, but it needs a couple of things doing to get it to work with the athena kernel
Click to expand...
Click to collapse
As I asked in private messages. can u make a tut for this specially how to work with your kitchen xip/sys porting section?
for some reason the kitchen seems to stop being able to port over a xip...I don't know if the copy I had somehow got corrupted on my drive but I'm going to redownload and try again.
has anyone else been having the problem?
lennie said:
for some reason the kitchen seems to stop being able to port over a xip...I don't know if the copy I had somehow got corrupted on my drive but I'm going to redownload and try again.
has anyone else been having the problem?
Click to expand...
Click to collapse
Lennie, this happened with my x7510 kitchen as well, the fix is to open the xip exporter tool bottom left of kitchen, there should be a button called something like, extract from payload? use that to extract the xip.old and see if that works
avengerpenguin said:
Lennie, this happened with my x7510 kitchen as well, the fix is to open the xip exporter tool bottom left of kitchen, there should be a button called something like, extract from payload? use that to extract the xip.old and see if that works
Click to expand...
Click to collapse
yeah it's there, but doesn't that mean I would have to have the os.payload for the newer rom that I want to get the xip from?
if I get a rom with build 28008 can I then use the kitchen to extract the os.payload and then use that to extract the xip.bin then use the xiporter in the kitchen and extract the xip? if i do that would it mess up the kitchen in anyway?
lennie said:
yeah it's there, but doesn't that mean I would have to have the os.payload for the newer rom that I want to get the xip from?
if I get a rom with build 28008 can I then use the kitchen to extract the os.payload and then use that to extract the xip.bin then use the xiporter in the kitchen and extract the xip? if i do that would it mess up the kitchen in anyway?
Click to expand...
Click to collapse
Sorry I thought you were having a different error relating to xip.old, from your pm I am assuming your not able to port the new xip.
I have used the msxip folder that comes with rom dumps to some success in the past by creating a new folder in kitchen/rom/shared/*create folder with new build number* copy the MSXIP Kernel folder into here for your new xip supplied with dump, and copy the packages.txt file from a working folder from another build.
(This is the new XIP files)
Then go to kitchen/rom/ATHE100/ *create folder with new build number* copy the OEMXIPKernel and packages.txt from a working ATHE100 folder into there.
(This is the old device specific xip part dumped from original rom)
You should find that you now have the new xip in the dropdown box of the kitchen, however I have found this very hit and miss and am currently struggling with porting 28014 using this method. If you search there are bits of advice about other tools able to dump XIP's that VK is not able to do, but I have not had the time to fully research it.
Let me know how you get on as my kitchen is currently crashing whenever I try and do this.
*Just found this http://www.everythingdiamond.info/showpost.php?p=2879&postcount=2 * See if this helps
avengerpenguin said:
Sorry I thought you were having a different error relating to xip.old, from your pm I am assuming your not able to port the new xip.
I have used the msxip folder that comes with rom dumps to some success in the past by creating a new folder in kitchen/rom/shared/*create folder with new build number* copy the MSXIP Kernel folder into here for your new xip supplied with dump, and copy the packages.txt file from a working folder from another build.
(This is the new XIP files)
Then go to kitchen/rom/ATHE100/ *create folder with new build number* copy the OEMXIPKernel and packages.txt from a working ATHE100 folder into there.
(This is the old device specific xip part dumped from original rom)
You should find that you now have the new xip in the dropdown box of the kitchen, however I have found this very hit and miss and am currently struggling with porting 28014 using this method. If you search there are bits of advice about other tools able to dump XIP's that VK is not able to do, but I have not had the time to fully research it.
Let me know how you get on as my kitchen is currently crashing whenever I try and do this.
*Just found this http://www.everythingdiamond.info/showpost.php?p=2879&postcount=2 * See if this helps
Click to expand...
Click to collapse
ok thanks. I'm giving it a try now, I put all the files in the place they're supposed to go however, I forgot what extension to rename BatchRecmod.jpg to (the file you had sent me)
EDIT: if I remember correctly BatchRecmod was a folder that you added the .jpg extension so you could send it to me, however, when I remove the extension I still can't access the contents inside...
lennie said:
ok thanks. I'm giving it a try now, I put all the files in the place they're supposed to go however, I forgot what extension to rename BatchRecmod.jpg to (the file you had sent me)
EDIT: if I remember correctly BatchRecmod was a folder that you added the .jpg extension so you could send it to me, however, when I remove the extension I still can't access the contents inside...
Click to expand...
Click to collapse
A better option than the batchrecmod I sent you would be to search Da_g's thread in dev/hacking for an addition to the kitchen made by user XTEP it adds the recmod function to the extra buttons inside the kitchen.
However if not change the .jpg extension to .zip and then unzip and you should have the files you need
avengerpenguin said:
A better option than the batchrecmod I sent you would be to search Da_g's thread in dev/hacking for an addition to the kitchen made by user XTEP it adds the recmod function to the extra buttons inside the kitchen.
However if not change the .jpg extension to .zip and then unzip and you should have the files you need
Click to expand...
Click to collapse
thank you very much, I think I found the addition by xtep in da_g's thread but I don't see how to add it to the kitchen...so I used the the files from the zip you sent me....I tried to cook and everything seemed as if it was going just fine, then bam! kitchen crashed. I'm going to try and get a working xip.bin to and see if the kitchen can extract it because using the msxipkernel does not seem to be a stable method.
lennie said:
thank you very much, I think I found the addition by xtep in da_g's thread but I don't see how to add it to the kitchen...so I used the the files from the zip you sent me....I tried to cook and everything seemed as if it was going just fine, then bam! kitchen crashed. I'm going to try and get a working xip.bin to and see if the kitchen can extract it because using the msxipkernel does not seem to be a stable method.
Click to expand...
Click to collapse
I have been struggling with this as well, I have not managed to find a portable xip.bin for 28014 as of yet. If you find one let me know please.