Database Users

EasyPortOven V2.2 [Updated May 11 2008]

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!!!

[APP] ReCOOKstruct - "all pkg in one" cooked ROM reconstructor

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?

[Q] Kitchen for HD mini

Dear developers,
can somebody answer which kitchen we can use for HD mini?????

Yup...EVK will be a good one for that...

Get the EVK kichen... find a stock HD MIni ROM... dump it using the EVK and get cooking!

Interesting.... i just want to say that you need to be carefull cause the HQVGA is an unussual size in new builds hopefully the rollup comes more often

+ Que PPC said:
Interesting.... i just want to say that you need to be carefull cause the HQVGA is an unussual size in new builds hopefully the rollup comes more often
Click to expand...
Click to collapse
com3.2 aka 231xx should come HVGA since thats the normal branch for the phone.

Johan Kraczmar said:
Dear developers,
can somebody answer which kitchen we can use for HD mini?????
Click to expand...
Click to collapse
OSKitchen should be able to dump and rebuild the ROM for that phone without any issue even if it's not in the list as long as you know how to rename the EXT packages to give them the right order (that's an issue you will also have with EVK but on EVK you'll probably have many more unless you use an adapted version for your phone with the right packages already recmodded inside).
BTW I'm working right now on a way to finally apply the DSM building order that all other kitchens seem to ignore to rebuild the latest phone ROMs 100% correctly.

airxtreme said:
OSKitchen should be able to dump and rebuild the ROM for that phone without any issue even if it's not in the list as long as you know how to rename the EXT packages to give them the right order (that's an issue you will also have with EVK but on EVK you'll probably have many more unless you use an adapted version for your phone with the right packages already recmodded inside).
BTW I'm working right now on a way to finally apply the DSM building order that all other kitchens seem to ignore to rebuild the latest phone ROMs 100% correctly.
Click to expand...
Click to collapse
Thank you for answer.
Can you help me with setting in htcrt_devices.ini ????

Johan Kraczmar said:
Thank you for answer.
Can you help me with setting in htcrt_devices.ini ????
Click to expand...
Click to collapse
osKitchen doesn't need that file because it automatically detects the NBH structure trough libNB; that's why I told you it should work even if the device is not on the supported list. As long as platformrebuilder doesn't cause some trouble (EVK is platformrebuilder-based too) oskitchen can work with any ROM as long as it can import and build the format (and NBH of course is supported).

Everything is clear.THX

airxtreme said:
BTW I'm working right now on a way to finally apply the DSM building order that all other kitchens seem to ignore to rebuild the latest phone ROMs 100% correctly.
Click to expand...
Click to collapse
Just a small correction here: Barin's OSBuilder does not ignore that issue. In fact there in a tool in his kitchen to modify packages.sof, so that you can even modify the build order. This is important when adding new packages which have .dsm not in stock roms, to ensure that they are build in the preferred order (ie: tweaks last).
@ OP, if you do use EVK to dump and build, be sure to clean the dump of duplicate files inside modules after dump, which is an issue with EVK's dump process. Also, with EVK (and likely OSKithcne) you need to recmod NTFConfig.dll to get a bootable rom. This is also not an issue with Barin's OSBuilder, which I highly recommend to every chef. I find this kitchen to be a superb tool compared to any kitchen to date.

mmmm interesting kitchen... lets try something new... cause the winmo times are getting bored this days

indagroove said:
Just a small correction here: Barin's OSBuilder does not ignore that issue. In fact there in a tool in his kitchen to modify packages.sof, so that you can even modify the build order. This is important when adding new packages which have .dsm not in stock roms, to ensure that they are build in the preferred order (ie: tweaks last).
Click to expand...
Click to collapse
I've never tried that kitchen however I can tell you that how I've implemented shadow ordering support is pure bliss. For example as you probably know HTC ROMs rely on many virtual packages (Project Default and others) to guarantee the building order and if you delete one of them (some of these packages are completely empty) everything breaks and that the shadow dependencies are often done on localized packages so changing language could also cause havoc.
In my kitchen I normalize all the packages dependencies during import so that all the dependencies on LCID folders and on those virtual folders are gone (so those can be safely deleted), I have a package property tab to set the shadow order of any package (if the DSM is not there it will be created), it has detailed checks for short circuits (infinite dependencies loop), etc. It's really, really well done.
indagroove said:
@ OP, if you do use EVK to dump and build, be sure to clean the dump of duplicate files inside modules after dump, which is an issue with EVK's dump process. Also, with EVK (and likely OSKithcne) you need to recmod NTFConfig.dll to get a bootable rom. This is also not an issue with Barin's OSBuilder, which I highly recommend to every chef. I find this kitchen to be a superb tool compared to any kitchen to date.
Click to expand...
Click to collapse
Well the two kitchens are in two completely different leagues: OSBuilder seems to be aimed to rebuild the ROM as best as possible following the microsoft standards (for example only flat packages, no EXT) while mine is aimed at offering the most complete and easy solution indeed the autoimport, (there is no informations associated to the device names in the import list, the kitchen finds everything out by itself to rebuild the NBH/BIN/TSW for that device), batch multi-language ROMs generation, easily structured UI and also all the warnings to limit user mistakes to minimum, from an easy automatically recmodding of packages that prb dislikes to much crazier extents like checking the Radio/splash files signatures are OK or making sure the user doesn't try to import packages from the wrong folder (like C:\) destroying his filesystem. Just because my kitchen is (sadly) still platformrebuilder-based it doesn't mean it has to be trashed though: as you may know Da_G is rewriting all the tools properly (100% compliant to the original standards) and I'm adapting his LibNB functions to the kitchen as soon as those became available hence the actual ability of dump/rebuild any NBH correctly without even knowing what device it is and hopefully soon internal XIP porting so that the kitchen will be already able (with extreloc for the IMGFS) to build its own ROMs for any device without any of the platformrebuilder limitations.

Learning to cook a rom

I've been reading up on cooking ROM's and with the help of leeston i managed to create a basic ROM earlier in the week. After searching for guides / tutorials on this stuff im really not that much the wiser, i cant seem to find anything that explains it well enough, there always missing details. The actual cooking process seems fairly straightforward but its those extra bits im missing ie
how do i add my own packages - am i right in just copying them to the SYS folder or is there more to it ?
how do i edit the registry - I know how to edit the registry once the ROM is loaded onto my phone but how do i do it from the ROM without the phone ?
how do i add things to the start menu - When i add packages to the SYS folder and load the ROM into my phone the shortcuts dont seem to be in my start menu
how do i add sense - i've loaded the packages but it never starts and theres no sense option in today settings
im new to this so as you'd imagine the questions i have are endless ...
Im sure most of this info is on XDA already somewhere but i just cant find it, maybe im searching for the wrong term or something.
Any help from the chef's would be great, perhaps you could provide links to tutorials / info you've used when learning to cook. Im sure this stuff would be useful to everyone and may even encourage more to have a go at cooking .

drkdeath5000 said:
1.how do i add my own packages - am i right in just copying them to the SYS folder or is there more to it ?
2.how do i edit the registry - I know how to edit the registry once the ROM is loaded onto my phone but how do i do it from the ROM without the phone ?
3.how do i add things to the start menu - When i add packages to the SYS folder and load the ROM into my phone the shortcuts dont seem to be in my start menu
4.how do i add sense - i've loaded the packages but it never starts and theres no sense option in today settings
.
Click to expand...
Click to collapse
I am still new to cooking but I'll tell you what i believe to be correct.
1.Yes. To add a package to a rom you put the package into the SYS folder.
However be aware that the kitchen used for the TG01 cannot handle EXT (visual) packages, only OEM (old) packages can be used. Use Totalfires package converter to convert between the 2 types.
The above info is not strictly true but is what you need to know when cooking for the TG and i don't have the time or knowledge to write a complete tutorial.
2. Editing the registry is all to do with .RGU files, you can create a package with a new one in or edit the existing ones within the packages in the SYS folder. You can edit them with notepad but i suggest using Notepad2.
Once you open an .RGU file you should recognize the reg key text in the file and edit it accordingly. As far as i am aware the file MUST have REGEDIT4 in the first line and an empty line at the bottom in order to work. Another way is to edit the regkey on your device then export the regkey using resco or something similar, then rename the resulting file from .reg to .rgu then open it in note pad and copy and paste it into another packages .rgu file, or create a custom package for that .rgu file.
The registry can also be modified using cab files during autorun, but this can be a little messy as the cab can be uninstalled by the end user causing problems.
3. To do this you need to edit the initflashs.txt file within the . This can be done manually or with one of the many package tools available on this site. The one i use is below, it does the hardwork for you, you click a few options and it edits the required files as needed.
4. Sense is a funny one. You should just need to add all the required packages to the SYS folder and away it goes. Unfortunately this is rarely the case. It should just a case of making sure all the sense packages are there, including its many dependencies. Sense is one of my weaker areas so maybe some one else has better advice.
Hope this is useful.

do you have a loooong far way, but read the forumposts an try, try and shortPin and try. that was my way, or is my way. i have don´t helping, all found with google and in xda forum.
unfortunately, my English knowledge is terrible. otherwise I would write more.
best to dump a officiels ROM or miROM5 , then you have an example
related post here
http://forum.xda-developers.com/showthread.php?t=750261
PC Software Reg-editor
http://ceregeditor.mdsoft.pl/index.php?id=1〈=en
CAB to OEM
http://forum.xda-developers.com/showpost.php?p=3942000&postcount=1
EXT to OEM
http://www.ppckitchen.org/forums/re...e666.ppckitchen.org/Tools/EXT%20to%20PPCk.exe
All folder to cooking need a .dsm (and/or) .rgu file
RGU name Generator (such as Reg- file) , dsm become automatically
http://www.famkruithof.net/uuid/uuidgen (Fetch UUIDs of another type to Version 4)
do you have a loooong far way!
... Or make a good donation to nokser or ffboy, they teach you

Hi my friend, I have a problem to cook a ROM with cab which required a reboot or witch have a information message ( SWYPE or GPSMOdDriver for example)
Do you know a solution for this please?
Thanks in advance.

Thanks for the info leeston and miro ;-). I havent had time to try it yet but will be over weekend and im almost sure now i know where to find the registry files ill be able to cook something decent up since that was my main problem. Thanks again for the help.
EVEALEX62 said:
Hi my friend, I have a problem to cook a ROM with cab which required a reboot or witch have a information message ( SWYPE or GPSMOdDriver for example)
Do you know a solution for this please?
Thanks in advance.
Click to expand...
Click to collapse
I may be wrong but when the cab files are first installed doesnt it automatically reboot ? If not you can always do a manual reboot ;-).

I've tried everything to get sense working but im just having no luck ... copied the packages to the sys folder, flashes fine, boots fine but no sense and now theres no setting shortcut in the start menu ?
Could i ask for the exact procedure for installing sense please ? Im getting my packages from here but replacing the 2017 home with 2016. Could i perhaps be missing something ?
Thanks again

drkdeath5000 said:
I may be wrong but when the cab files are first installed doesnt it automatically reboot ? If not you can always do a manual reboot ;-).
Click to expand...
Click to collapse
I have try to delete the line "Reboot" after autocabinstall but nothing change the phone always reboot ... I think the only thing is to do OEM package...
I have test with many cabs but nothing works same as you with Sense ...
Have you found solutions ?

EVEALEX62 said:
Hi my friend, I have a problem to cook a ROM with cab which required a reboot or witch have a information message ( SWYPE or GPSMOdDriver for example)
Do you know a solution for this please?
Thanks in advance.
Click to expand...
Click to collapse
The solutoin is to use autorun instead of cabinstl, you can then write a custom script to handle the input required by the cab.
However this is above my head, and i couldn't get autorun to work. FFBOY knows how but i doubt you will get his help as he doesn't seem to check any threads other than his own rom threads, and if he does his responces are few and far between.

drkdeath5000 said:
I've tried everything to get sense working but im just having no luck ... copied the packages to the sys folder, flashes fine, boots fine but no sense and now theres no setting shortcut in the start menu ?
Could i ask for the exact procedure for installing sense please ? Im getting my packages from here but replacing the 2017 home with 2016. Could i perhaps be missing something ?
Thanks again
Click to expand...
Click to collapse
Those are the packages i used and they work so it's not the packages, but i cheated and dumped a sense rom then modified it. I don't have time to try and work out how to do it properly unfortunatley.

leeston2379 said:
Those are the packages i used and they work so it's not the packages, but i cheated and dumped a sense rom then modified it. I don't have time to try and work out how to do it properly unfortunatley.
Click to expand...
Click to collapse
Well atleast i know the packages are fine, i was starting to wonder if that was the problem . Theres some satisfaction in doing it yourself but like miro said i think its just too much for me, ill give it another go later in the week and if that fails ill just dump a sense rom like you did ... if there was just a tutorial on installing sense packages etc id be fine, with sense being so popular you'd think there to be loads of tuts.

[SOLVED]First boot customization doesn't start

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!