Hi!
This tool tries reconstruct cooked ROMs, that have been cooked using the "all packages in one" feature. It does this using a scaffold ROM, that should be as identical to the cooked one as possible for maximum recookstruction.
How does it work?
In theory
It loads the filenames and registry entries from the mock-up ROM and from the dumped ROM (using rgucomp to get the registry informations), then it tries to set up the same file and registry structure that the scaffold ROM had, but with the files and registry entries from the dumped ROM.
In practice
Copy the "oem", "sys" and "packages" directory from a non-cooked ROM in a directory. This will be the scaffold. The more identical this is to the cooked ROM the better. You can of course use a kitchenized official ROM too.
Next extract the contents of the cooked ROM. (using imgfstodump or something similar). Put the contents of the ROM in a "dump" directory besides the "oem", "sys" and "packages" directory.
Delete the dsm file from the dump, you won't need it. If it has an rgu file, delete it too.
Next copy reCOOKstruct into this directory, and run it (you should do it in a console, so you can see what it is doing). After a while it should create an "_output" directory, with the "oem", "sys" and "packages" directories recookstructed. All files and registry entries it couldn't handle using the scaffold will be put in the "Unknown packages" package in the "packages" directory.
Recooking
If you want to cook the recookstructed dump, then move everything from the "packages" directory to the "OEM" directory (they won't have an option.xml so buildos won't recognize them is they are there). Add ".ROM" and ".VM" to the "sys" directory from the dump (because they weren't copied). Next load up buildos, and cook. Be careful though! You will need the same (extracted) XIP in your kitchen as the dumped ROM had! Copying and porting XIP's in not in the scope of this topic...
Legal
If you recookstruct a ROM and use information from it to create your ROM, then add credit to the original author even if he didn't release his rom in kitchen form
Download
see attachments
EDIT: forgot to include rgucomp.exe, added
Awesome concept if it works. Ill give it a shot later when I get by a real computer thanks
hey sztupy great tool bro im gonna take a look at it (sector)!
thanks
will try tis ... really getting tired of the all in one package ... when wanna recook
kudos
rjmjr69 said:
Awesome concept if it works. Ill give it a shot later when I get by a real computer thanks
Click to expand...
Click to collapse
I've tried with two of my favorite ROM's (that have no kitchens) and it worked fine. Just don't forget to use the XIP/os.nb/"etc stuff not related to the imgfs section" from the cooked rom.
ugotta try this. thanks
Hi,
i have tested your tool, but comes error:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\BlackStoneKitchen>recookstruct
ReCOOKstruct
Cooked ROM reconstructor
by SztupY (http://winmo.sztupy.hu)
Reading data from dump
Reading dumped filelist
Reading registry hives
dumping dump/boot.hv
C:\DOKUME~1\alle\eee\eee.recookstruct.exe.2\app\recookstruct.rb:85:in ``': No su
ch file or directory - rgucomp -o "dump/boot.hv" -nologo (Errno::ENOENT)
from C:\DOKUME~1\alle\eee\eee.recookstruct.exe.2\app\recookstruct.rb:85
from C:\DOKUME~1\alle\eee\eee.recookstruct.exe.2\app\recookstruct.rb:83:
in `each'
from C:\DOKUME~1\alle\eee\eee.recookstruct.exe.2\app\recookstruct.rb:83
from C:\DOKUME~1\alle\eee\eee.recookstruct.exe.2\bootstrap.rb:77:in `loa
d'
from C:\DOKUME~1\alle\eee\eee.recookstruct.exe.2\bootstrap.rb:77
C:\BlackStoneKitchen>
Click to expand...
Click to collapse
C:\DOKUME~1\alle\eee\eee.recookstruct.exe.2\ what is it???
solution?
Folderstructure:
BlackStoneKitchen
-Dump
-OEM
-SYS
cheers
*_Touch_HD_* said:
Hi,
i have tested your tool, but comes error:
C:\DOKUME~1\alle\eee\eee.recookstruct.exe.2\ what is it???
solution?
Folderstructure:
BlackStoneKitchen
-Dump
-OEM
-SYS
cheers
Click to expand...
Click to collapse
it couldn't find rgucomp.exe. Did you copy that there too?
EDIT: I forgot to include rgucomp.exe in the zip. Redownload please.
nice, now works.
cheers
yes yes sztupy...
always re-inventing the wheel. Gonna use this methinks....
Thanks as always bro. Hope you keeping well!!
Ok so if I read this right what needs to happen is you have to find the DONOR rom which is most likely a stock or leaked rom and then the actual rom your want to depackage and follow the rest of the directions?
Can someone please verify this for me before I screw something up. Thanks
Would someone be willing to do a rom for me I think this is above my skills but I have a base rom I'm dieing to add too
rjmjr69 said:
Ok so if I read this right what needs to happen is you have to find the DONOR rom which is most likely a stock or leaked rom and then the actual rom your want to depackage and follow the rest of the directions?
Can someone please verify this for me before I screw something up. Thanks
Would someone be willing to do a rom for me I think this is above my skills but I have a base rom I'm dieing to add too
Click to expand...
Click to collapse
Yes, you're right. You'll need a donor that will be used as a pattern for the recookstruction. You can use anything ranging from official ROM's to kitchens with extracted ROM's
sztupy said:
Yes, you're right. You'll need a donor that will be used as a pattern for the recookstruction. You can use anything ranging from official ROM's to kitchens with extracted ROM's
Click to expand...
Click to collapse
Thank you sir for such a speedy reply. I've given it a shot but I dont know what the heck is going wrong I think its Vista even though I have full admin "hidden admin" user rights.
I'm going to have to fire up the xp machine see what happens there. But I would still love if someone could do it for me hehehe
rjmjr69 said:
Thank you sir for such a speedy reply. I've given it a shot but I dont know what the heck is going wrong I think its Vista even though I have full admin "hidden admin" user rights.
I'm going to have to fire up the xp machine see what happens there. But I would still love if someone could do it for me hehehe
Click to expand...
Click to collapse
vista shoudln't be a problem, I'm using Win7/vista miyself
Another fine thread added to my list of subscriptions ...
Cheers!
hilaireg said:
Another fine thread added to my list of subscriptions ...
Cheers!
Click to expand...
Click to collapse
This thread wouldn't be possible without your cooking tutorial
SztupY
can i reconstruct a rom that was made by another chef? if so how because i read everything and i am still clueless on what to do
Wooooooowwwwwwwwwww! Works great!! PROPS man!!
Oh wait, then it failed in SYS at sys/Redist_Lang_0409
Says: (** are username, disregard please)
C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:215:in `conv': "\343o Tom\351 and Pr\355n"... (Iconv::IllegalSequence)
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:215
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:214:in `open'
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:214
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:185:in `each'
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:185
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\bootstrap.rb:77:in `load'
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\bootstrap.rb:77
Any ideas??
Very much appreciated. I was in the process of developing the same exact thing. But you seem to have beat me to the punch. At least you made my job easier. lol
ookba said:
Wooooooowwwwwwwwwww! Works great!! PROPS man!!
Oh wait, then it failed in SYS at sys/Redist_Lang_0409
Says: (** are username, disregard please)
C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:215:in `conv': "\343o Tom\351 and Pr\355n"... (Iconv::IllegalSequence)
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:215
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:214:in `open'
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:214
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:185:in `each'
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\app\recookstruct.rb:185
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\bootstrap.rb:77:in `load'
from C:\DOCUME~1\**\eee\eee.recookstruct.exe.3\bootstrap.rb:77
Any ideas??
Click to expand...
Click to collapse
Iconv crashed because it expected an UTF-8 string but got something else. What locale are you in?
Related
The Scoter Kitchen team is proud to release the first release of the kitchen. This kitchen incorporates all the tools used by Oki and the rest of the team to decode, modify, and rebuild ROMs. It includes a help system that is meant to be clear to new users, and useful to old pros. Of course, this is only the first release, and thus will have bugs, and areas in need of improvement. This Kitchen is based on Bepe's WM5 Kitchen, and many of his tools. Special thanks to Mamiach, itsme, machinagod, gmap, buzzlightyear, and many others. Oki started the initiative, and we in the team are grateful for allowing us the privilege of contributing. There are also many additional tools not directly used for general ROM analyzing that can be found throughout. The kitchen is designed to be sleek and clear for the new user, while still containing all relevant tools for every part of the build process. This post is one of many across multiple forums. We are opening up development to all, and ask for volunteer translators. We will coordinate through forums primarily, but later plan on PM's, e-mail, etc. to effectively coordinate further development of the Scoter Kitchen. In addition, the kitchen is designed to extract most HTC ROMs, but it has it's limitations in the tools included, and the outlined process which are in the help files. Again, this will become better implemented through the help of the community. Now though this Kitchen is designed primarily for the Scoter, we intend to make this kitchen the primary hub for all PDA customization across all WM5 platforms. This post will be posted on many forums, and since the team members communicate primarily w/ English, we ask that those respond to this thread in English, or at least include an English translation. As a last note, you are solely responsible for any damage to your device or computer that might result from the use of the Scoter Kitchen, or any of it's parts. The following posts are left blank and will be filled w/ info later. Here are the download links:
http://www.MegaShare.com/107480
http://rapidshare.com/files/15460590/Scoter_Kitchen_1.0.exe.html
Regards,
Jason
Kitchen Team Members
Oki
JKR
DwD
Theo - Greek translation
Nadavi
gerttom
Preaper
Friends of the kitchen
Bepe (done as much as any other member and is considered an incredible contributor, and even that doesn't give him enough credit)
Kinger
blueboy
Marshal
cyril - French translation
bakker_be - Dutch and German translation
kterz
Regards,
Jason
Reserved,
Regards,
Jason
Bakup Files Of 0 Bytes
i had done a backup with ur utilites but the size of BDK0,BDK1 & BDTL0 is 0 byte why it is so ?????????? I stop here and wating for reply
to bad these dont work for the hermes .nb and .nbh files.. hopefully in the future it can be integrated..
shogunmark said:
to bad these dont work for the hermes .nb and .nbh files.. hopefully in the future it can be integrated..
Click to expand...
Click to collapse
Yep, we plan to add the nbhextract to the tools. And as far as the backup utility, that only works for the Scoter. We don't own htc devices, so that why we've asked the community to fill in the gaps. The extraction is universal, since there will be back and forth on various ROMs. The ROM installer also only works for the scoter. So, some info on these and anything else that the HTC community would like added, just tell us how. We can't really test these things, so we rely on you guys. At some point, the installer will ask what device you have, and install apps that apply to your individual devices.
Regards,
Jason
thats cool.. integrating the the hermes stuff will be difficult at this time anyway since we dont have a good set process on everything, we are still fighting the possibility of bad nand blocks with some cooked roms.. Something that i think would be really cool would be a full blown GUI with all these features built in..
here's some release notes I posted over at Buzz's site
JKR said:
4d45h said:
Questions.....
1. What is OS.bat. It says missing OS.bat when I click Cooker and start the build OS.
2. Where do you put pakages inside LOC(Bepe ways of cooking)
3. What is CEImage.bin? Is it the same as nk.nba base ROM Bepe ways.
Thanks and what a great tool.
Click to expand...
Click to collapse
1. That is a file created when you decode a ROM. I'm not sure what exactly it is for, bepe could answer that.
2. You can't use the current Kitchen ROM archives. The Scoter Kitchen incororates some more advanced versions of bepe's apps. The best way to describe the current situation is that bepe's WM5 Kitchen is version 1.0, and the Scoter Kitchen is 2.0. Since bepe was a big part of the Scoter Kitchen development, this should make sense. Keep in mind that this is not ready to be a replacement to bepe's kitchen yet, because it is only setup for building ROMs for the Scoter. We released it to all for many reason: 1) To speed up the development of the Kitchen for use w/ other devices, 2) it currently seems to be the most complete set of tools and help files for decoding ROMs, 3) the help files have a lot of info that may be interesting to many users. Most notable tools from bepe that are in the Scoter Kitchen are: DMP2PKG.exe, and PKG2DMP.exe. These tools actually have their own UI's that are fairly impressive. So to answer you question, you'd need to decode your current ROM and then begin modify that. Oki is the ROM hacker on the team. Essentially what he does, is extract the drivers (in the OEM folder) from various ROMs for our device, picks the best ones, adds in the SYS files and then puts in the packages for various apps. Anyways, bepe combined the LOC and SYS folders together into the SYS folder. for aesthetic reasons, the SYS folder is referred to as the OS folder in the build room. This is only a short cut name, and actual folder is still called SYS and is located in the Utilities folder.
3. Yes, this is in the help files in file:///C:/Scoter%20Kitchen/Utilities/Tools/Excess%20stuff/J-Guide/Extraction%20Room.htm?zoom_highlight=.bin .nb, .bin, and .nba are handled in the same way. just copy the location i posted into your browser address box.
Regards,
Jason
Click to expand...
Click to collapse
JKR said:
A few release notes. The install directory is C:\Scoter Kitchen. You will also see an uninstall script in c:\. This obviously uninstalls the Kitchen, everything is removed (including any work files in the kitchen) except the desktop shortcut. Also, since the imgfs tools are used so much by ROM cookers including myself, the Kitchen will place a copy of the imgfs tools in the %SystemRoot%\system32\ directory. This allows these tools to be opened by any command box w/o having to change directories. As you explore the kitchen you will see readme files in almost all folders, describing what is in that particular folder. Lastly, you will see like 15 command box shortcuts throughout the kitchen, this just makes things easier since their working DIR is the one they are placed in.
Regards,
Jason
Click to expand...
Click to collapse
Nobody here seems to be too forthcoming w/ info about other devices. Now I could go and search for all this info on my own, but then I probably wouldn't have the time or energy to modify the kitchen accordingly. W/ that said, I'll list some specific questions.
1. What programs are required for installing ROMs on various devices, and what are the procedures?
2. Are other devices capable of changing just the CE image through the boot loader, or does this have to be done using itsme tools? And what is the procedure?
3. Is the page pool setting in the same address on all HTC ROMs, or does this vary from model to model?
4. Explain the whole IPL and radio rom issue.
5. What would you like added to this kitchen?
You could just point me to specific posts too. Like I said, the Kitchen is completely functional for us Scoter guy's, so we won't spend the hours and hours required to research this stuff, since we won't get any benefit. But if some direction is given, we are willing, and wanting to expand our kitchen for use w/ other devices.
Regards,
Jason
I thought that it is just for Mio, and a little more documentation to it will be nice, thanks
xplode said:
I thought that it is just for Mio, and a little more documentation to it will be nice, thanks
Click to expand...
Click to collapse
Well it is fully functional for the Mio, but most all tools are here on this site. The two things specific to the Mio are the ROM backup utility, and the ROM update utility. Everything else applies to the HTC community. We are hoping that somebody will point us in the right direction for the equivalents of the two previously mentioned tools. Now as far as the documentation, yes, we plan to expand it. However, what specifically do you feel should be added?
Regards,
Jason
First of all, this's a very FANTASTIC tool!
In the BEPE's ROM Kitchen, there's an initflashfiles.txt file in the folder of each OEM apps which is used to create shotcut or copy/move files, its content will be combined with others into the initflashfiles.dat. Does this file still make sense in your kitchen?
BrightMoonHeart said:
First of all, this's a very FANTASTIC tool!
In the BEPE's ROM Kitchen, there's an initflashfiles.txt file in the folder of each OEM apps which is used to create shotcut or copy/move files, its content will be combined with others into the initflashfiles.dat. Does this file still make sense in your kitchen?
Click to expand...
Click to collapse
yep
Regards,
Jason
@JKR
I have reach up to using the DMP2PKG.exe stage, which can see the files in the *.dsm (see attached pic).
How to extract the files in the *.dsm?
How do I use RECMOD.exe?
CWKJ said:
@JKR
I have reach up to using the DMP2PKG.exe stage, which can see the files in the *.dsm (see attached pic).
How to extract the files in the *.dsm?
How do I use RECMOD.exe?
Click to expand...
Click to collapse
Hi,
You probably read the help files, huh? Yeah, those are dated, my bad. You don't actually have to touch DMP2PKG. The extract modules/files has dmp2pkg already scripted. At the time I wrote the help file, bepe didn't allow for command line commands. He has since, and I have scripted for it since. The following is an excerpt that I post over at Buzz's site.
JKR said:
Ahhh, I see problem. the .dat file needs to be in one of the folders, the OEM one i think. When Oki (rom team member) creates a file set, he includes the .dat file in the same folder that mxip_lang.vol is in, on our device it's 6acba9af-b4de-c7a3-802b-91ff1f140caf, but is probably different on yours. Anyways, I'm not sure where you got the idea to drag those to the tools folder, if it's in the help file, please tell me where. I've just re-looked at the help files, and they are quite dated. I've added a lot of automation to the process. Sorry for that. The correct procedure to extract a rom and rebuild it is to extract a .bin, .nba, .nb, or .nb0 file from your rom image. Then drag it to the extract modules. Open in another window the build room. put the .dat file (if it was placed in the modules folder) in the OEM folder. Drag all the contents of the OEM folder to the OEM shortcut in the build room. Drag all the contents of the SYS folder to the OS shortcut. Place the .bin or equivalent file in the rom template folder, and place the boot.rgu file in the \rom template\xip folder. The boot.rgu may be different for different devices, so use one that works on your device. I don't remember where exactly we got ours from, but I think it may have been from bepe's file set for his kitchen. Now launch the cooker. In the end, you should have a .bin file in c:\Scoter kitchen, aka one level up from the build room. hmmm, looks complicated. This is in the help files, but like I said, I need to update them, we were anxious to release the kitchen, since it had been under development for so long.
Regards,
Jason
Click to expand...
Click to collapse
As one more note, you probably wouldn't have to worry about the missing entries in the dmp2pkg interface. Probably just dated references from your ROM, it's a custom ROM?
Regards,
Jason
The rom is custom rom by Helmi, AKU3.5 v1.3, see my signature.
I will take sometime to digest you writings.
Still have not able to extract the *.dll, *.exe, *.hv, etc.
Will try adding & delete files later.
@JLR
I am back, manage to get some time to try the extract problem I faced.
Thanks, the extract works.
See the attached zip file of extracted files' directory list.
I have some questions,
1. what "<DIR> SYS" does, seems to have some *.dsm and some repeated DLLs.
2. If I do not need some *.exe, *.lnk, *.etc files, I just delete them?
3. How do I know that I fully deleted the files related to the feature that I do not want?
4. How do I know which corresponding *.dsm to be deleted?
5. How do I know which files goes to which directory in the \Windows\ of PPC?
6. How do I add files, how do I know what *.dsm to add and the name of the directories with very long string.
Questions please...
What is the importance of extracting files compared to extracting modules?
I have a base nbf file that I converted to nba file, that I want to modify to add the apps to build the ROM, I am confused as to which one I need, is it the files or the modules?
Great work! Thx for very useful tools!
What about map.txt support that helps to replace the GUIDs with the actual Package Names? I seen it in Bepe's kitchen...
JKR said:
Reserved,
Regards,
Jason
Click to expand...
Click to collapse
I need help. I was able to run the cooker file without any errors. Now what?
How can I recreate the .nbf file? Where can I find it? Should I be looking at the DUMP folder?
Hi, I dont know how Rom Kitchen Cooker were doing this till date ( some like me just ignored in past) but some how i got this (iv not created it) and would like to share this.
1) Place ur OEM, with its dsm file inside.
2)take out option.xml temporarily
3)Drag and drop OEM folder over BuildDSM.exe
4)u got ur dsm populated.
5)place back option.xml in OEM folder, and thats done.
View attachment BuildDSM.zip
BTW, I always leave my Option.xml in the OEM. Never had a problem
looks very nice does it work for system dsm's?
Midget_1990 said:
looks very nice does it work for system dsm's?
Click to expand...
Click to collapse
ya its working on sys dsm's also.
looks easy, i look forward to trying it, great work.
oww..!
nandlal_mk.Thanks a lot..!
Trying now..!
Thanks man !
I'll use it now.
I had hard time locating this one. Good thing you sent the link in the pm
To be honest I dont quite get what this does. I thought that for OEM packages we make, we just need a zero-bite file with the GUID and .dsm in the end.
WizeMan said:
To be honest I dont quite get what this does. I thought that for OEM packages we make, we just need a zero-bite file with the GUID and .dsm in the end.
Click to expand...
Click to collapse
Yes, but that would result with "missing" packages
Aha, Uhum, I Get it.
Is that really all the need and reason to use a populated DSM?
So that when the Rom gets extracted there won't be missing files?
So Empty Bites DSM have no effect on performance or whatsoever?
(Except the fact they or 0 bites)
I've got 2 small questions;
1. Can somebody explain to me what the function of these *.dsm files is?
2. Wouldn't it be nicer to exclude the option.xml file automatically instead of taking it out by hand?
But as far as I can understand it looks very promising!!!
Great tool, just trying it today, big thanks !!!
Is there an option to bypass the "press a key to continue" ?
looks easy, trying it, great work.
Thank you very much.
The system cannot execute the specified program.
Requires:
Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)
http://www.microsoft.com/downloads/...D9-AE1A-4A14-984D-389C36F85647&displaylang=en
... installing VC2K5 SP1 Redist allows the application to run although Dependency Walker also shows a delay-load on DWMAPI.DLL.
This is a release for my ROM porting kitchen. It ports both XIP's and SYS folders. It currently supports the following:
Herald
Wizard
Prophet
Kaiser
Elf/Elfin
Hermes
Zinc
Athena
http://www.darthnet40.com/xda/ivanmmj/Kitchens/
(You will need 7-Zip to open the file.)
This is compatible with Bepe's extended kitchen, but I don't believe he ever released one for every device out there. It requires a ROM folder with an extracted XIP folder within it. Just download the Herald's and you'll see what I mean. The ONLY tested section has been the Herald section as that's the only device that I have.
If your device is compatible with Bepe's kitchen or my kitchen, it will automatically launch the kitchen right after.
Instructions:
Delete your old SYS folder
Place the SYS file you wish to port into Working_Folder
Place your xip.bin that you wish to port into the Prepare folder
*Note: Close the XIPPort program after pressing "Make Packages." The script will take over after that.
You should not have a Working_Folder with an OEM, SYS and XIP folder (and a Tools folder if you have Bepe's kitchen, even more if you have my kitchen.)
Double click on the RunMe file and choose your device.
For those who have a kitchen:
Place bepe's kitchen in the Working_Folder (so that OEM/SYS/ROM and other folders are right within Working_Folder.) Alternatively, you can place also place all the files into EasyBakeOven's folder. Allow the Working_Folder to override EasyBakeOven's Working_Folder. You will not loose any data but will bypass a few "info" scripts. This will not cause any problems.
Obligatory Warning Label:
Use this at your own RISK. I cannot be held liable for any damage caused to your device by your own mistakes or by my mistakes in the instructions.
If you wish to know how to do this manually, head over to my HowTo thread.
Thank you's go to:
Bepe for his Extended kitchen and Herald/Atlas files
ababrekar for the elfin files
l3v5y and xvx45 for the Prophet files
character and ginminded for the Wizard files
Script for the Kaiser files
tjkhattak61 for the Atom Exec files
cruzzmz for the Zinc files
caxio for the Hermes files
irus for the Athena files
Changelog
V2.2
Added Athena Compatibility
V2.1
Added Prophet Compatibility
Added Elfin/Elf Compatibility
Added Hermes Compatibility
Added Kaiser Compatibility
Added Zinc Compatibility
Added Atom Compatibility
V2
Added Wizard Compatibility
Rewrote script to add expandability
V1.5
XIP porting complete
V1
SYS porting complete
Woo! I've failed to find a link for this up till now, but now I can cook some new ROMS!!
One thing, the read me doesn't include some of the more reason compatibility improvements...
Welcome to EasyBakeOven!
Devices supported:
Herald/Atlas
Wizard
Note: Make sure that the XIP in your recieving folder has been extracted already (You should have a ROM folder with a XIP folder inside it.) This is not an issue if you're using Bepe's Extended 6.1 kitchen or my own JustClean EasyBakeOven.
Thank you's go to:
Bepe for his Extended kitchen and Herald/Atlas files
ababrekar for the elfin files
l3v5y and xvx45 for the Prophet files
character and ginminded for the Wizard files
Script for the Kaiser files
tjkhattak61 for the Atom Exec files
cruzzmz for the Zinc files
caxio for the Hermes files
irus for the Athena files
Click to expand...
Click to collapse
l3v5y said:
Woo! I've failed to find a link for this up till now, but now I can cook some new ROMS!!
One thing, the read me doesn't include some of the more reason compatibility improvements...
Click to expand...
Click to collapse
Noted. Thank you!
Has anyone found this even remotely useful? If not, I will not pursue adding more devices.
Has anyone found this even remotely useful? If not, I will not pursue adding more devices.
Click to expand...
Click to collapse
I have! I've ported a Kaiser XIP and a Touch one to the Prophet! Problem is I couldn't find the latest builds so they where slightly out of date...
l3v5y said:
I have! I've ported a Kaiser XIP and a Touch one to the Prophet! Problem is I couldn't find the latest builds so they where slightly out of date...
Click to expand...
Click to collapse
Just for being nice to me, here you go!
That's the newest official build. Be careful of anything "newer," they're fakes.
It's the one labeled 19213.7z
You'll need 7Zip to open the file. In it as the xip.bin and the SYS folders.
Yay!!!
Porting time!
I have one feature request!
Would it be possible to build a feature in that cleans out the folders before porting?
I think I'll test later cause actually I'm in exam but I think it work, I'm on the same device as l3v5y so I'll make my test and maybe take to you Artemis files (my other phone)
Thank for your hard work
Great tool ivanmmj.... I have a few questions. I guess I don't fully understand the process.
I've been able to get the XIP folder, os.nb.payload and romhdr.bin files from a KAISER rom... plus I used the .VM and WinCENLS_WWE folders from a working HERMES rom, but I can't seem to get past the second boot screen. A question I had is... do we use the os.nb.payload and romhdr.bin we got from the KAISER? or do we use those from a working hermes rom? and the XIP directory, do we need to change anything in there? or is just extracting it out, enough to work?
Thanks in advance.
Awesome tool, looks like a dummy can me even port ROM's will try it out sometime. Thanks bunches!
l3v5y said:
I have one feature request!
Would it be possible to build a feature in that cleans out the folders before porting?
Click to expand...
Click to collapse
Already ahead of you. Today I noticed that I tend to leave a mess behind. lol I'll have it remove the files before replacing them, then I'll have it delete the extra files created during the process when it's done. (This part is already ready but I just haven't uploaded it. The removing the files before replacing them, I haven't done so, yet. Although this might not really be needed. Only the cleaning after part.)
...Maybe I don't know what you're talking about. lol
Explain it to me.
AssassinsLament said:
Great tool ivanmmj.... I have a few questions. I guess I don't fully understand the process.
I've been able to get the XIP folder, os.nb.payload and romhdr.bin files from a KAISER rom... plus I used the .VM and WinCENLS_WWE folders from a working HERMES rom, but I can't seem to get past the second boot screen. A question I had is... do we use the os.nb.payload and romhdr.bin we got from the KAISER? or do we use those from a working hermes rom? and the XIP directory, do we need to change anything in there? or is just extracting it out, enough to work?
Thanks in advance.
Click to expand...
Click to collapse
You need the XIP folder, os.nb.payload and romhdr.bin of YOUR device and the xip.bin and SYS folder of the rom you want to port INTO your device. Which device do you have? Tell me and I'll "draw" a map of what goes where.
xvx45 said:
I think I'll test later cause actually I'm in exam but I think it work, I'm on the same device as l3v5y so I'll make my test and maybe take to you Artemis files (my other phone)
Thank for your hard work
Click to expand...
Click to collapse
That would be more than welcomed especially since I'm gonna use my Herald cooking class and modify it to teach Artemis users, also.
ai6908 said:
Awesome tool, looks like a dummy can me even port ROM's will try it out sometime. Thanks bunches!
Click to expand...
Click to collapse
My hope is that it will allow just about anyone to port a ROM. ^_^
ivanmmj said:
You need the XIP folder, os.nb.payload and romhdr.bin of YOUR device and the xip.bin and SYS folder of the rom you want to port INTO your device. Which device do you have? Tell me and I'll "draw" a map of what goes where.
Click to expand...
Click to collapse
Thanks for replying ivanmmj... I have a hermes, and I've been doing exactly that... my problem is when I go to build it, I get "An unhandled win32 exception occurred in buildxip.exe [2276]"
If I put in my older XIP build, buildxip works fine... so I'm lost now. Oh, and I'm trying to port the 19213 official att kaiser rom XIP.
AssassinsLament said:
Thanks for replying ivanmmj... I have a hermes, and I've been doing exactly that... my problem is when I go to build it, I get "An unhandled win32 exception occurred in buildxip.exe [2276]"
If I put in my older XIP build, buildxip works fine... so I'm lost now. Oh, and I'm trying to port the 19213 official att kaiser rom XIP.
Click to expand...
Click to collapse
You'll need:
OEM: hermes
ROM folder: Hermes (uncluding the XIP folder and all the other files)
SYS folder from kaiser (look for and remove MSkernel from this folder... I'm not 100% on that folder yet and future versions may handle that folder automatically)
Place the xip.bin from the kaiser into the prepare folder.
Now run the RunMe
ivanmmj said:
You'll need:
OEM: hermes
ROM folder: Hermes (uncluding the XIP folder and all the other files)
SYS folder from kaiser (look for and remove MSkernel from this folder... I'm not 100% on that folder yet and future versions may handle that folder automatically)
Place the xip.bin from the kaiser into the prepare folder.
Now run the RunMe
Click to expand...
Click to collapse
I really appreciate your help ivanmmj, same thing again. It chokes up on BuildXIP.exe ...I have BuildXIP version 0.53 if that makes any difference. I tried with two XIP versions... 19209 and 19900. I'm about to give up.
Oh and I have Visual Studio 2008 installed, so I don't think it would be the runtimes... would it?
AssassinsLament said:
I really appreciate your help ivanmmj, same thing again. It chokes up on BuildXIP.exe ...I have BuildXIP version 0.53 if that makes any difference. I tried with two XIP versions... 19209 and 19900. I'm about to give up.
Oh and I have Visual Studio 2008 installed, so I don't think it would be the runtimes... would it?
Click to expand...
Click to collapse
It might be.... I'll have to do some research...
Ok, I even installed the vs2008 runtimes, same thing.. I found buildxip v.54, same thing... then i moved the whole ROM folder (new XIP) out and put in the old 19209 one and it ran... so maybe there's something wrong with 19213 with hermes? ok, I give up. Thanks for your help!!
19213 porting to elfin
i'm trying to port the 19213 to my elfin, and after porting when i use bepe's kitchen, it gets stuck at this screenshot. anybody help!!!
This post is obsolete
Thank you very much for this!
EDIT:
Only these two folders? No more or do I have to replce the folders inside of my Kitchen?
I took the liberty to changing the Title to Internet Explorer and Giving you Bump in informing you.
Hope people get the intention of this thread, so hopefully there won't be hundred's of different IE versions around.
Have you Seen PIE8 yet?
HI!!!
I am looking forward the PIE6 such a long time!!!
Thank you very much!!
But I want to know " Can it be uninstall to roll back to PIE4???"
Thanks!!!
Noonski said:
I took the liberty to changing the Title to Internet Explorer and Giving you Bump in informing you.
Hope people get the intention of this thread, so hopefully there won't be hundred's of different IE versions around.
Have you Seen PIE8 yet?
Click to expand...
Click to collapse
Hi Noonski, yes I already have Internet Explorer version 8 for a few days. Not tested yet. I uploaded it to mediafire so you can download the cab here. I didn't make an OEM package yet.
animelover said:
Only these two folders? No more or do I have to replce the folders inside of my Kitchen?
Click to expand...
Click to collapse
I would like to know as well what SYS packages (if any?) should be removed before putting this in the kitchen?
Andy
i installed mi ie8 cab on my hp ipaq 214. but i dont know how to start it. where is exe?
so I tried instaling the cab file and I do not see any differences. It seems like an addon for the already existing PIE... ?
I looke at the OEM, and I am not sure what the differences are other than the new DLLs.
Can someone explain what the new features are?
I still can't see the myspace page normal. WTF?!
Ok guy more details...
The oem package must go in Sys folder togehter other Browsing folders, you must not delete anything!
Cook your room and enjoy, rember tu put flashlite also in your rom!
For IE8 probably need some other file, I'll try to cook in a rom to try it!
robertus3d said:
Ok guy more details...
The oem package must go in Sys folder togehter other Browsing folders, you must not delete anything!
Cook your room and enjoy, rember tu put flashlite also in your rom!
For IE8 probably need some other file, I'll try to cook in a rom to try it!
Click to expand...
Click to collapse
That explains it. I was going to report back as not working but i might try that and check back later.
I tried the Package both in OEM and Sys, iT did not change anything here to.
More Play tomorrow.
**** Just Noticed this was Post Number 3000 for me.
Noonski said:
I tried the Package both in OEM and Sys, iT did not change anything here to.
More Play tomorrow.
**** Just Noticed this was Post Number 3000 for me.
Click to expand...
Click to collapse
Congrats on that.
Did you try the first root folder and put the two inner folders in the sys?
Repack posted in post #1, this should work.
I have cooked this into my ROM and it all works OK apart from the IE home page. In the folder 'browsingie_LANG_0409' the .RGU file sets the home page to
Code:
"home_0409"="file://\\Windows\\iemo6_default_0409.htm"
and this file is included in the folder. When I launch IE though I get the 'Action canceled' page. I have verified the file is there and if I use File Exlporer to find the file and then open it, it all opens OK. If I open the file this way and then set it to the home page and then close and open IE the problem is still there so I am stuck as to what the issue is?
I have noticed similar behaviour with other .htm files as well; for example the JBlend0409.htm file when trying to access it via Help - you get 'Cannot open Help. The file cannot be found' however the file is there and the shortcuts are correct?
It is pretty weird?
Andy
Hi Guys
I am using a HTC hermes. I just upgraded my device with wm6. I used offficial upgarde from AT&T. After upgrading the internet explorer is not working. Need help to solve the problem. With thanks
Pump Man
Hi,
I'm using the latest osKitchen (v1.33.5) to build my own ROM for the HTC Kovsky (SE Xperia X1). Followed the tutorial, imported the latest official R3A WWE build, added a WM 21916 build and started cooking. But there's no first boot customization after a flash/hard reset. There are no errors, executing AutoRun.exe from the Windows folder doesn't seem to work either.
The config.txt (used by AutoRun and RunCC) files are left stock, but editing them doesn't make a difference. How can I fix this? If you need more information, just ask. I'll reply asap.
Have you added the runcc.lua file and redirected it to the right config.txt?
If so, flash the ROM and look whether those files are in \Windows\ (and just not executed) or not present.
Flashed the ROM: runcc.lua was already added and it redirects to the right config.txt. Paths are correct.
...
this happened to me not so long ago:
check that the autorun.exe and config**.txt files do not get overwrote during rom creation.
check that there are no duplicate files with those file names..
good luck!
Rn
I don't think those files are being overwritten during ROM creation. How can I check this? Can't find the Autorun.exe in the kitchen but after building and flashing it is visible in the Windows folder on the device. There are no duplicate files, triple checked that.
Tried building a new kitchen from scratch, an untouched build (only importing the stock ROM and the 21916 build) didn't have a first boot customization either.
I remember figuring this out on my X1 a year ago was a pain in the a*s. Can't recall where the problem was anyway. I could upload my OEM Packages for you if you'd like to? I'm using a older version of that kitchen anyway so this "could" lead to new problems...
That would be great! Please let me know what kitchen version you used, if there are any problems I can try to roll back to that one.
I PM'd you. Most persons would not know what to do with said files so it makes no sense posting them here I guess...
...
hey dude,
not sure what your problem is if all your config**.txt are there and there is no duplicate files, for me i had a mortscript called "autorun.exe" which obviously overwrote my original autorun.exe and caused my device to do no customisation.
erm, as for not finding your autorun.exe
lots of files in the kitchen are hidden and the windows hidden files toggle does not show all the hidden files for some reason :/
me personally i use ACDSee photo manager 9 to view the files in my kitchen, i then select all the files and untick the 'hidden' properties.
ALL the files you couldnt see in windows explorer are always visable using Acdsee, by unticking the properties with Acdsee, it now makes them visable in windows explorer.
hope you understand what i meen :s
btw, i only use acdsee9 to view my pictures and to change the properties of the files.
i edit all my images with photoshop and paint.
Rn
derliebewolf said:
Most persons would not know what to do with said files so it makes no sense posting them here I guess...
Click to expand...
Click to collapse
According to my searching results this issue seems to be very rare. Posting the download link here shouldn't harm others.
For osKitchen version number you mentioned in your PM, open the kitchen and use Help -> About. Don't know if this option was present in earlier builds, but at least in 1.33.5 it is.
raving_nanza said:
erm, as for not finding your autorun.exe
lots of files in the kitchen are hidden and the windows hidden files toggle does not show all the hidden files for some reason :/
Click to expand...
Click to collapse
I wasn't at the stage of using Mortscript in my ROMs yet. Untoggle hidden system files in Windows folder options did the trick, I found AutoRun.exe
Now I'm gonna sit and wait until the download is available...
DillonDarko said:
I wasn't at the stage of using Mortscript in my ROMs yet.
Click to expand...
Click to collapse
let me know when you are at that stage dude, ive got a small collection of usefull scripts that might prove themselves usefull.
DillonDarko said:
Untoggle hidden system files in Windows folder options did the trick, I found AutoRun.exe
Click to expand...
Click to collapse
cool man, but remember:
the windows hidden files toggle does not show all the hidden files.
Acdsee will show them all so none are hidden, trust me
Rn
NVM....thought of a some other problem...
raving_nanza said:
let me know when you are at that stage dude, ive got a small collection of usefull scripts that might prove themselves usefull.
Click to expand...
Click to collapse
Will do.
For the others that might experience this problem, the download link for EXT and OEM packages available here. These packages are untested, but I'm cooking them now. Thanks for the help. Scroll down for the fix.
So I think it's working now?
@All: please be aware, those packages are device-specific and for HTC Kovsky / SE Xperia X1!
Ok, tried replacing the existing packages with those from derliebewolf. Even when left untouched or using different (correct) commands there's still no customization. @derliebewolf, could you upload your "osKitchen.exe" and "Resources" directory for me? It's all I need, I can fill the kitchen from scratch there.
If this turns out to be a kitchen specific problem I won't hesitate posting it in the official osKitchen thread.
This is a pretty complicated problem to give advise.
Just a suggestion, didn't you modified/removed something from your initflashfiles.dat?
I mean the startup.
Compair it with a stock rom if you did and check if something is missing.
On my HD2:
Directory("\Windows\StartUp"):-File("ConfigureDevice.lnk","\Windows\ConfigureDevice.lnk")
Directory("\Windows\StartUp"):-File("bugtrap.lnk","\Windows\bugtrap.lnk")
Directory("\Windows\StartUp"):-File("HTCStartUp.lnk","\Windows\HTCStartUp.lnk")
Directory("\Windows\StartUp"):-File("PKG.lnk","\Windows\PKG.lnk")
Directory("\Windows\StartUp"):-File("SignatureReplace.lnk","\Windows\SignatureReplace.lnk")
Directory("\Windows\StartUp"):-File("Welcome.lnk","\Windows\welcome.lnk")
Click to expand...
Click to collapse
You tried everything possible so I taught maybe this could be possible.
On Xperia it's probably about the same.
DillonDarko said:
Ok, tried replacing the existing packages with those from derliebewolf. Even when left untouched or using different (correct) commands there's still no customization. @derliebewolf, could you upload your "osKitchen.exe" and "Resources" directory for me? It's all I need, I can fill the kitchen from scratch there.
If this turns out to be a kitchen specific problem I won't hesitate posting it in the official osKitchen thread.
Click to expand...
Click to collapse
You really need to leave the welcome.lnk line in there, or else you won't get the alignment screen and you can't boot the device up.
Found the issue: an incomplete initflashfiles.dat. By adding the lines below to a stock initflashfiles.dat the whole issue has been fixed.
Code:
Directory("\Windows\StartUp"):-File("CheckAutoRun.lnk","\Windows\CheckAutoRun.lnk")
Directory("\Windows\StartUp"):-File("AutoShortcut.lnk","\Windows\AutoShortcut.lnk")
Turned out a stock initflashfiles.dat file doesn't have those lines included by default. Thanks to all for the help, expect a new custom Xperia X1 ROM soon.
That's nice to hear, congrats.
Please at [SOLVED] to the topic title and I will link this thread to the solved cases sticky.
DillonDarko said:
Found the issue: an incomplete initflashfiles.dat. By adding the lines below to a stock initflashfiles.dat the whole issue has been fixed.
Code:
Directory("\Windows\StartUp"):-File("CheckAutoRun.lnk","\Windows\CheckAutoRun.lnk")
Directory("\Windows\StartUp"):-File("AutoShortcut.lnk","\Windows\AutoShortcut.lnk")
Turned out a stock initflashfiles.dat file doesn't have those lines included by default. Thanks to all for the help, expect a new custom Xperia X1 ROM soon.
Click to expand...
Click to collapse
DillonDarko said:
Found the issue: an incomplete initflashfiles.dat. By adding the lines below to a stock initflashfiles.dat the whole issue has been fixed.
Turned out a stock initflashfiles.dat file doesn't have those lines included by default. Thanks to all for the help, expect a new custom Xperia X1 ROM soon.
Click to expand...
Click to collapse
Which makes me woder whether those lines are missing in my initflashfiles.dat as well? RunCC is working perfectly anyway... Glad you solved it!