Database Users

[SOLVED]Cooking themes into ROMs

Hi
How does one cook a custom theme into a ROM and make that the default theme? I've tried editing quite a few registry entrys and it still does not work.
Another question along the same lines, how do i cook in a custom today wallpaper? I've tried changing registry entrys here as well but it didn't work either
Thanks
Mod edit: Solved thread

well...
long history here...
First.. the themes for 6.5 and 6.5.X are not the same theme, so genereally if you want to cook inside a theme that you have made... simply be sure that you have a TSK that contains all the registry entries for images and the two images in JPG format with your size screen set them as "read only" and "archive" attribs then save the cab as winmo cab then rename it from .cab to .tsk then.... put it into a EXT pkg in your EVK kitchen or whatever you have EVK or OSK make a pkg called "my theme name" inside a folder called "FILES" inside that folder all images of the theme and the TSK too... then go to your RUNCC or autoinstall or however you have and set in the txt file this comand...
TSK: \Windows\My theme name.tsk
at the end of the file this way in the botting procces frist customization the theme will be set as default
is the dirt way but you can make it safely instead of changing many regs that simply you will forgot the original
Y'all must to remember that if you want to patch the theme or install a them in a runing working rom in teh device you must to trust sign the TSK but if you are cooking the kitchen will do it for you

The wall paper is easy: just set whatever pic you want as the wallpaper using either Home-settings or the pic and video tool. Then open \windows, and look for the newest files. You'll see two files named stwater_###x###.png or something very similar (could be tdywater). Grab these two files and then when you're editing a .tsk file, include the files in it. Now you're done.
If you want to cook the theme straight into the rom, then you need to dump all of the reg keys and put them into an app.reg file in a package that runs at the end of the build. Name your two wallpaper files (portrait and landscape) "classicblue_stwater_480_640.jpg" and "classicblue_stwater_640_480.jpg," and stick them in the same EXT. (To get the proper names for your device, look in (SYS\Build#\dpi_192_resh_480_resv_640\COMMON\base_dpi_192_resh_480_resv_640), obviously with the proper resolution.) Look through your add2config.txt or config.txt files, and make sure that no other stock .tsk is run during customization.

I know i to cook a theme and set as default and blabla....but its interesting know how to trust sign the TSK when i make a theme.cab to put in a working rom...can you explain?
+ Que PPC said:
Y'all must to remember that if you want to patch the theme or install a them in a runing working rom in teh device you must to trust sign the TSK but if you are cooking the kitchen will do it for you
Click to expand...
Click to collapse

A way that bobsbbq has taught me, and has worked for a 6.5.5 theme
make a new folder in your EXT packes, called whatever the theme is, and in there make another folder called files, in the files folder copy across everything in the theme's cab. then go back into the root of the themes package folder and make a new text document called add2config in there paste the following:
TSK: \Windows\XXXX.tsk
where XXXX is the exact name of yout .tsk file found in the themes cab (so it will also be in the files folder if you want to copy the file name exactly.
Save the text document and then just select it in your kitchen

af974 said:
I know i to cook a theme and set as default and blabla....but its interesting know how to trust sign the TSK when i make a theme.cab to put in a working rom...can you explain?
Click to expand...
Click to collapse
If you try to sign a cab with the last year SDK certs you will have an error is better you to trust sign your cabs reading this article
http://forum.xda-developers.com/showthread.php?t=650309

Thanks guys for the replies I ended up using Farmer Ted's method and it's working exactly how I wanted it to.
BTW: Farmer Ted, whenever I ask for help, whether on this forum or another, you're always among the first to help me. HUGE thanks dude

Thanks Que,
This is very usefull for me
+ Que PPC said:
If you try to sign a cab with the last year SDK certs you will have an error is better you to trust sign your cabs reading this article
http://forum.xda-developers.com/showthread.php?t=650309
Click to expand...
Click to collapse

No prob dude... BTW ppl understand that...
If you want to make fixes for your ROM....
YOU MUST!! to make a trusted sign cab with signed files inside...
if you want to cook the fix... so the kitchen will sign all of them

+ Que PPC said:
No prob dude... BTW ppl understand that...
If you want to make fixes for your ROM....
YOU MUST!! to make a trusted sign cab with signed files inside...
if you want to cook the fix... so the kitchen will sign all of them
Click to expand...
Click to collapse
i dont understand why we have to sign a cab file, when we remove certs in kitchen?
Code:
..\TOOLS\implantxip -xip xip.bin -payload OS.nb.payload -imgstart %imgstart% -%uldr% -pp 16 -%nocert%
ive never signed a cab file in my life and they always install fine

I've never signed a cab, either. EVK makes it too easy, lol.

+ Que PPC said:
well...
long history here...
First.. the themes for 6.5 and 6.5.X are not the same theme, so genereally if you want to cook inside a theme that you have made... simply be sure that you have a TSK that contains all the registry entries for images and the two images in JPG format with your size screen set them as "read only" and "archive" attribs then save the cab as winmo cab then rename it from .cab to .tsk then.... put it into a EXT pkg in your EVK kitchen or whatever you have EVK or OSK make a pkg called "my theme name" inside a folder called "FILES" inside that folder all images of the theme and the TSK too... then go to your RUNCC or autoinstall or however you have and set in the txt file this comand...
TSK: \Windows\My theme name.tsk
at the end of the file this way in the botting procces frist customization the theme will be set as default
is the dirt way but you can make it safely instead of changing many regs that simply you will forgot the original
Y'all must to remember that if you want to patch the theme or install a them in a runing working rom in teh device you must to trust sign the TSK but if you are cooking the kitchen will do it for you
Click to expand...
Click to collapse
I started having problems with Farmer Ted's way so I tried this one instead. It works perfectly except for one thing, that it needs a restart before it's effective. Is there any way to get it working on first boot?

I use this one:
OEM\ExtendedPKG\config.txt
Code:
LOCK:Enabled
TSK: \WINDOWS\Htc_black.tsk
LOCK:Disabled
RST: Reset
This will set that theme on first boot, of course you need to have RunnCC running.
You must change Htc_black.tsk with your tsk name.
seeM_ZA said:
I started having problems with Farmer Ted's way so I tried this one instead. It works perfectly except for one thing, that it needs a restart before it's effective. Is there any way to get it working on first boot?
Click to expand...
Click to collapse

af974 said:
I use this one:
OEM\ExtendedPKG\config.txt
Code:
LOCK:Enabled
TSK: \WINDOWS\Htc_black.tsk
LOCK:Disabled
RST: Reset
This will set that theme on first boot, of course you need to have RunnCC running.
You must change Htc_black.tsk with your tsk name.
Click to expand...
Click to collapse
I did mine exactly like that but it doesn't work. It only works after I reboot the phone atleast once
EDIT: I noticed if i go to settings/home, it is set as the default theme (it's hilighted) but it's not actually visible anywhere.
EDIT2: Never mind it's sorted out. I went back to Farmer Ted's way and got it to work exactly how I wanted it.

Hi guys,
How can I change cooked in wallpaper if my theme doesn't contain a wall?

Farmer Ted said:
The wall paper is easy: just set whatever pic you want as the wallpaper using either Home-settings or the pic and video tool. Then open \windows, and look for the newest files. You'll see two files named stwater_###x###.png or something very similar (could be tdywater). Grab these two files and then when you're editing a .tsk file, include the files in it. Now you're done.
Click to expand...
Click to collapse
I believe this is what you want to do

[★] said:
A way that bobsbbq has taught me, and has worked for a 6.5.5 theme
make a new folder in your EXT packes, called whatever the theme is, and in there make another folder called files, in the files folder copy across everything in the theme's cab. then go back into the root of the themes package folder and make a new text document called add2config in there paste the following:
TSK: \Windows\XXXX.tsk
where XXXX is the exact name of yout .tsk file found in the themes cab (so it will also be in the files folder if you want to copy the file name exactly.
Save the text document and then just select it in your kitchen
Click to expand...
Click to collapse
Does this method select the theme on 1st boot?
btw, how do you select a default Wallpaper for Manila's Home Tab?

sometimes you need to take your theme tsk rename it to .cab open it with cab manager and change the pics inside
the manila use as default a pic inside the EXT or OEM pkg it contains the manila app... search for the image and just replace it same size, and attributes.

+ Que PPC said:
sometimes you need to take your theme tsk rename it to .cab open it with cab manager and change the pics inside
the manila use as default a pic inside the EXT or OEM pkg it contains the manila app... search for the image and just replace it same size, and attributes.
Click to expand...
Click to collapse
Thanks. Will try it out

what would the image name be? in EXT Manila.exe is only in Manila_Core and I don't have any image there except Manila files...
In OEM I saw the default HTC Black.tsk along with HTC stwater images...
Do I need to replace these 2 Images (HTC Black Stwater... 480x800 and 800x480)?

[SOLVED] UC cant install a cab "Sleuth's UC"

Can someone explain this to me, cause everything I read shows me I am doing this right but yet I am getting an error still.
I added a cab to the operatorpkg folder: tilt2keyboard.cab
I then went to the ExtendedPkg folder and modifed the config.txt to this:
LOCK:Enabled
CAB:\windows\tilt2keyboard.cab
LOCKisabled
RST: Reset
flashed the rom, and then get an error during the customizing stating:
Error
\windows\tilt2keyboard.cab is not found
When I take the line out of config.txt. and flash it, I look in the windows folder, and the cab is right there plain as day. Its attribute is read only, its not hidden or anything and its driving me insane cause everything I read I did exactly.
I even went to convert this to a EXT Package and still couldnt get it to install that way either.
What am I doing wrong or missing?

You are missing a "space" in the cab line
Code:
CAB: \windows\tilt2keyboard.cab

suggestion: dont set read only, and set hidden to that cab

Diegis0n,
Ur kidding? *&(^%%&^* that was it? going to try this right now.
Que PPC, okay why hidden just curious?

Nope didnt work Now I get the error:
Error
Install \windows\tilt2keyboard.cab failed, code 0x80070005
Both hidden and unhidden.

Bump? Any other ideas?

AngelDeath said:
Bump? Any other ideas?
Click to expand...
Click to collapse
I'm out of ideas mate
The way i do it is by using Sleuth255's UC: http://forum.xda-developers.com/showthread.php?t=366337

Check your security policies.
Code:
;---- disable security check for installed programs
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000101a"=dword:00000001
"0000101C"=dword:00000001

Would that be in the boot.rgu file?
Or where would I find that before cooking?

AngelDeath said:
Would that be in the boot.rgu file?
Or where would I find that before cooking?
Click to expand...
Click to collapse
CAB: \Windows\tilt2keyboard.cab
Click to expand...
Click to collapse
copy the above to your config file.
you should put those reg settings into the app.reg and .rgu of the last Package in the extend packages section,providing that you are using visual kitchen.

Attempting again now. Just added the entries to the .reg and .rgu of zlibce file if my understanding was correct. Will update after cooking and flashing!

Just add this package to your Ext section of the kitchen.

Thank you both Indagroove, and Faria, without that zip I got it to work. But I will add that to the end of my EXT.
But to both of you: Thank you very much.

AngelDeath said:
Thank you both Indagroove, and Faria, without that zip I got it to work. But I will add that to the end of my EXT.
But to both of you: Thank you very much.
Click to expand...
Click to collapse
Glad to help.

Solved thread
Hiden cab...? well i use hidden cabs in my poor UC to simply dont have more files to load when i go to my windows folder, thats the only reason.

[FYI] If a .provxml seems to not work in your coked ROM, Try this

The attached .provxml will not execute. It's supposed to associate icons with folders in the start menu, but it's just not working. It is totally unmodified from the Rhodium S2 ROM. The directories are there as the initflashfiles.dat file is unmodified and the folders are in the start menu. Anyone care to help?

Your file is fine so I guess that you have the same issue I had .
I guess you don't have that provxml added to any of dsm files . Just use this tool and add it to any of dsm files.
http://forum.xda-developers.com/showthread.php?t=523139
You can also use xml parser to check if file is good, for example Serna Editor.
Click to expand...
Click to collapse
Maybe I'm wrong, so if you already have this provxml added to any of dsm files, we'll look for more reasons. One more question, do you try to cook this into ROM or execute from Advanced Configuration Tool?

It's cooked in. The package is directly from the Rhodium S2 ROM, so I don't quite understand why it's not executing. I'm thinking about putting it in another OEM folder and seeing if that will help. Heck I'm lost, and about to turn it in for the night.

As I wrote, try adding it manually to dsm file in that OEM folder, this should help you, if this won't help, then I'm out of ideas.
Anyway, you can just add content of that provxml to another provxml, it's dirty way but probably the easiest one.

This happens because the messenger.lnk have not been created when this provxml is executed and it fails.
So just rename the provxml to mxipupdate_zprojectdefault_a_000.provxml
Notice the "z" ahead of the project.
This trick will put the provxml after the mxipupdate_windowsliveim_1.provxml, so the messenger.lnk will have been created and the provxml will run just fine.

But he said that provxml isn't excuted at all, I'm out of ideas . Anyway, it's worth to give your idea a try.

jwzg said:
The attached .provxml will not execute. It's supposed to associate icons with folders in the start menu, but it's just not working. It is totally unmodified from the Rhodium S2 ROM. The directories are there as the initflashfiles.dat file is unmodified and the folders are in the start menu. Anyone care to help?
Click to expand...
Click to collapse
the provxml isn´t executed on my rhodium as well. but renaming to mxipupdate_zzzzprojectdefault_a_000.provxml
does work for me.
as the posters above me wrote:
the problem seems to be the messenger package which includes another *provxml file which should be prozessed BEFORE mxipupdate_projectdefault_a_000.provxml but it isn´t! also *.provxml aren´t prozessed if there´s a failure inside. when you remove a program and you don´t clear the line in the *.provxml the file would not me prozessed.
this problem is related to platformrebuilder breaking something, you can pm airxtreme for info, it seems that he solved this problem in his wonderful kitchen
steph

Provxml can be launched but they stops at the line it find a problem so it seems that it doesnt works.
Platform rebuilder can reads DSM in EVK? or just in OsK? or none?

Renaming the .provxml solved the issue. Man, the start menu looks good now! Thanks!

Great, I wouldn't think about renaming on my own . Anyway, it seems that those provxml files are processed in alphabetical order, right?

everything is alphabetical order processed in platform rebuilder based kitchens ¬¬
Mod edit: Solved

Dude!!! The sameprob here with Leo ROM... same file... going to try your tip!

kurniawan77 said:
Dude!!! The sameprob here with Leo ROM... same file... going to try your tip!
Click to expand...
Click to collapse
@kurniawan77 - Did it work for you?
Same prob here, using osKitchen Zero for HTC LEO. Already tried renaming by adding zzz in name and also tried adding the provxml in dsm. Any other suggestions? This is drving me nuts, please help.
p/s: also tried opening the provxml in internet explorer/XML notepad 2007 - no errors. Made sure there are no "<?xml version="1.0" encoding="utf-8" ?>" in the headers.

Try to replace platformrebuilder.exe with another version, that did the trick for me.
Before you ask, sorry but I'm using a private edition of platformbuilder so I can't share.
I'm using platformrebuilder.exe v.2.1.0.0
tidus18 said:
@kurniawan77 - Did it work for you?
Same prob here, using osKitchen Zero for HTC LEO. Already tried renaming by adding zzz in name and also tried adding the provxml in dsm. Any other suggestions? This is drving me nuts, please help.
p/s: also tried opening the provxml in internet explorer/XML notepad 2007 - no errors. Made sure there are no "<?xml version="1.0" encoding="utf-8" ?>" in the headers.
Click to expand...
Click to collapse

tidus18 said:
@kurniawan77 - Did it work for you?
Same prob here, using osKitchen Zero for HTC LEO. Already tried renaming by adding zzz in name and also tried adding the provxml in dsm. Any other suggestions? This is drving me nuts, please help.
p/s: also tried opening the provxml in internet explorer/XML notepad 2007 - no errors. Made sure there are no "<?xml version="1.0" encoding="utf-8" ?>" in the headers.
Click to expand...
Click to collapse
You still have problems even with oskitchen 1.31beta3? Some people reported the new DSM-based provxml order to be working fine.

Evil Provxmls....
airxtreme said:
You still have problems even with oskitchen 1.31beta3? Some people reported the new DSM-based provxml order to be working fine.
Click to expand...
Click to collapse
Hi Airxtreme - Thanks for developing the kitchen! Its really great. But i just recently moved to osK Zero from ervius. Previously in ervius i didnt even bother to add provxmls in any dsm. I dont quite understand DSM management fully, but i did add the provxmls in DSM of my ext package (ext package contains my custom icons for start menu and the provxml to add reg entries).
When i get back home, i will try to rebuild the ROM with older version of kitchen and report back. Currently im using v1.31Beta3.
p/s: i had trouble with theme provxmls as well, finally i had to put all the theme files in Operatorpkg, and put the xml entries in HTC's provxmls (the one named HTC_100) for it to work.

Laurentius26 said:
Try to replace platformrebuilder.exe with another version, that did the trick for me.
Before you ask, sorry but I'm using a private edition of platformbuilder so I can't share.
I'm using platformrebuilder.exe v.2.1.0.0
Click to expand...
Click to collapse
2.1.0.0? Then what's the version that is publically available? And can you say something about the new functions, etc.? Thanks!

tidus18 said:
Hi Airxtreme - Thanks for developing the kitchen! Its really great. But i just recently moved to osK Zero from ervius. Previously in ervius i didnt even bother to add provxmls in any dsm. I dont quite understand DSM management fully, but i did add the provxmls in DSM of my ext package (ext package contains my custom icons for start menu and the provxml to add reg entries).
When i get back home, i will try to rebuild the ROM with older version of kitchen and report back. Currently im using v1.31Beta3.
p/s: i had trouble with theme provxmls as well, finally i had to put all the theme files in Operatorpkg, and put the xml entries in HTC's provxmls (the one named HTC_100) for it to work.
Click to expand...
Click to collapse
Those having problem with provxmls where it is used to overwrite other provxmls in sys (ie: for theme settings), please try this http://forum.xda-developers.com/showpost.php?p=7038082&postcount=2477
This version of your kitchen solved all my probs. THANKS!!!!!!!!!!!!

I only tried to help make the provxml load
Bepe created the kitchen tool and knows everything about it.
Edit; a bit late but the version I use is 2.1.0.0 indeed.
cnzqy1 said:
2.1.0.0? Then what's the version that is publically available? And can you say something about the new functions, etc.? Thanks!
Click to expand...
Click to collapse

tidus18 said:
Those having problem with provxmls where it is used to overwrite other provxmls in sys (ie: for theme settings), please try this http://forum.xda-developers.com/showpost.php?p=7038082&postcount=2477
This version of your kitchen solved all my probs. THANKS!!!!!!!!!!!!
Click to expand...
Click to collapse
glad it worked out for u... been away for days... working on bugfixes... and more. v1.31b3 from worked out even better... sorry for late response

[TOOL 4 CHEFS] kitchen UPDATE ONLY NEW EXT batch file (EVK & OSK compatible)

only new ext-pkg's to a other kitchen (language import support is coming...).
a friend of mine wrote a little bat-file for me and i want to share it with you.
the creator insisted to call it bloody rudimentary but i think it's quite useful.
he wants to stay anonymous...
around two hours of brainwork (i remember the command for this... what was it again?) and notepad.exe to create this from scratch.
you only need to adjust the two paths at the beginning.
the batch searches for same packets (exact name matches) and ignores them.
a txt will pop up showing only the new packages.
you can edit this list (only delete pks but don't change entries).
save and close after you removed the lines you don't want to import.
batch will create a temp workfolder in c: (it will pop up once copying is finished).
at this point you can rename the folders (add *_photon_1.36 at the end for example)
and add missing language sub-folders.
if you are done, press any key at the cmd window and all the edited/renamed package folders will be moved to the ext-folder in the destination kitchen (_NewPackages folder).
example (if you want to update only new ext from 1.36 into 1.11 kitchen):
-kitchen1 (source kitchen) photon 1.36 htc
-kitchen2 (destination kitchen) photon 1.11 vodafone
tested and working with oskitchen1.31beta10 file-/folder-structure.
take this code and save it into a txt file. rename it to *.bat and adjust the paths.
Code:
@echo off
REM ------- EDITABLE SECTION
SET L_SOURCEPATH="[COLOR="Red"]X:\osKitchen Zero v1.31beta10_1.36SOURCE\Sources\Devices\HTC HD Mini\EXT Packages\HTC HD Mini Packages\[/COLOR]"
SET L_TARGETPATH="[COLOR="Red"]X:\osKitchen Zero v1.31beta10_1.11DESTINATION\Sources\Devices\HTC HD Mini\EXT Packages\HTC HD Mini Packages\[/COLOR]"
REM ------ END
SET L_WORKPATH=C:\SCRWORK
MKDIR %L_WORKPATH%
SET SCRFILE=%L_WORKPATH%\packets_source.txt
SET TGTFILE=%L_WORKPATH%\packets_target.txt
SET ACTFILE=%L_WORKPATH%\PKG2COPY.TXT
del %ACTFILE%>nul
CD %L_SOURCEPATH%
DIR /B>%SCRFILE%
CD \
CD %L_TARGETPATH%
DIR /B>%TGTFILE%
CD \
FOR /F "delims=" %%I IN (%SCRFILE%) DO (
REM <--------------------------------------------------------------
REM insert logic here to select packages i.e. package numbers
FINDSTR /C:"%%I" %TGTFILE%>nul&& ECHO Exact name match. || ECHO "%%I">>%ACTFILE%
REM insert some better logic here duh!
REM <--------------------------------------------------------------
)
CLS
ECHO !!!! Remove packages you dont want to copy from list but RETAIN LINE FORMAT !!!!
ECHO !!!! Save and close List to continue!!!!
start /w notepad %L_WORKPATH%\PKG2COPY.TXT
REM hier: Collect packages based on pkg2copy.txt
CD %L_SOURCEPATH%
FOR /F "delims=" %%I IN (%ACTFILE%) DO (
xcopy /E /Y /H /I %%I %L_WORKPATH%\PRECOPY\%%I
)
CLS
ECHO !!!!Edit Folders now!!! Add langs etc.. press any key to continue and copy edited folders to destination (_NewPackages)
REM <--------------------------------------------------------------
REM i.E. delete... rename....
explorer %L_WORKPATH%\PRECOPY\
REM automate it duh!
pause
REM <--------------------------------------------------------------
REM !!! ACTION - Copy from Precopy to Target Folder (Targetpath\_NewPackages)
xcopy /E /H /Y /I %L_WORKPATH%\PRECOPY\*.* %L_TARGETPATH%\_NewPackages\
rmdir /s /q %L_WORKPATH%
explorer %L_TARGETPATH%
CD \

tested now with ervius visual kichen.
works. hope y'all enjoy this batch file...
please leave a "thanks" if you like and use it.
thanks

wow this tool is awesome, its amazing how a simple batch file created by notepad can do so much functionality..
gonna use this right now
thanks..

my opinion:
many xda-chef's would use it if they would know about it's existence..
please help me to keep this thread alive so all chefs can see it better...
tell your favorite chefs to take a look at this thread. thanks.

Wow, the time this is going to save me! (^^,) I haven't used it yet but I'm pretty sure I will. Thanks bro!

enjoy......

I didnt try it yet but sounds like a very life saver tool, got one week sticky for let other chefs to check it.
Thanks for sharing.
@ mods: i will take care of unsticky it @ 04 August.

I'm sorry but I've read the intro 3 times and still don't know what it does.

As i said ,i didnt try it yet but for what i understood it updates packages in your EXT folder,example:
You have a 2.14 Leo Kitchen and you want update only NEW EXT packages from 3.04.
Laurentius26 said:
I'm sorry but I've read the intro 3 times and still don't know what it does.
Click to expand...
Click to collapse

feel free to test it. no harm done.
source and destination folders stay untouched.
only the (not exact name match - packets that aren't already in the destination kitchen) packets you don't delete from the pop-up list will be copied to the destination kitchen ext folder (_NewPackages subfolder).

I will give it a shot when I'm back from holiday mate.
Thanks for sharing with us.
HD2Owner said:
feel free to test it. no harm done.
source and destination folders stay untouched.
only the (not exact name match - packets that aren't already in the destination kitchen) packets you don't delete from the pop-up list will be copied to the destination kitchen ext folder (_NewPackages subfolder).
Click to expand...
Click to collapse

wauw!!! works great man!!! perfect! now the only thing is we need to automate copying lang files from an other folder... hihi

kurniawan77 said:
wauw!!! works great man!!! perfect! now the only thing is we need to automate copying lang files from an other folder... hihi
Click to expand...
Click to collapse
You mean for SYS?

seeM_ZA said:
You mean for SYS?
Click to expand...
Click to collapse
i guess he means lang folders for ext-packages since this tool has nothing to do with sys.
it's possible but it would require a more advanced detection logic.

seeM_ZA said:
You mean for SYS?
Click to expand...
Click to collapse
Nah... not that much work...

Unfortunately, my kitchen is setup in a way that would prevent this from working, but this seems like a great idea.
Thanks for sharing!

HD2Owner said:
my opinion:
many xda-chef's would use it if they would know about it's existence..
please help me to keep this thread alive so all chefs can see it better...
tell your favorite chefs to take a look at this thread. thanks.
Click to expand...
Click to collapse
This is all nice and cool.. but what happened to porting your packages MANUALLY and actually looking at them before you put them in your kitchen ? You can't tell me this is how you cook a ROM... you run this batch file and blindly move over "newer" packages to your kitchen ? Wow... I believe packages need to be looked over and brought it one by one to insure compatibility first.

NRGZ28 said:
This is all nice and cool.. but what happened to porting your packages MANUALLY and actually looking at them before you put them in your kitchen ? You can't tell me this is how you cook a ROM... you run this batch file and blindly move over "newer" packages to your kitchen ? Wow... I believe packages need to be looked over and brought it one by one to insure compatibility first.
Click to expand...
Click to collapse
you are right... that's why the tool moves the new ext folders into a sub-folder (_NewPackages).
cooks still need to add compatible lang sub-folders and maybe adjust some keys in the rgu's.
this batch-file is only around a week old. so it's basically new.
the main reason for it's existence is to remove the manual package comparison wich is very time-consuming (detection of already present packages).
of course cooks need to check the new ext like they would need to do when updating them manually.
in my personal kitchen i adjust the ext folder names as following:
Album_3_2_19203733_0_leo_1.66
Album_3_2_20132625_0_leo_2.13
Album_3_2_20161229_00_leo_3.04
Album_3_2_20171628_00_huashan_0.90
this way i always know where the ext's in my kitchen are coming from.
the batch file detection still works when adjusting the end of the folder names.
for example:
source kitchen-Album_3_2_19203733_0
destination kitchen-Album_3_2_19203733_0_leo_1.66
the album folder will still be ignored even after you changed the folder name of the already imported package to Album_3_2_19203733_0_leo_1.66.
just don't change/rename the blue part (original package name)

HD2Owner said:
you are right... that's why the tool moves the new ext folders into a sub-folder (_NewPackages).
cooks still need to add compatible lang sub-folders and maybe adjust some keys in the rgu's.
this batch-file is only around a week old. so it's basically new.
the main reason for it's existence is to remove the manual package comparison wich is very time-consuming (detection of already present packages).
of course cooks need to check the new ext like they would need to do when updating them manually.
in my personal kitchen i adjust the ext folder names as following:
Album_3_2_19203733_0_leo_1.66
Album_3_2_20132625_0_leo_2.13
Album_3_2_20161229_00_leo_3.04
Album_3_2_20171628_00_huashan_0.90
this way i always know where the ext's in my kitchen are coming from.
the batch file detection still works when adjusting the end of the folder names.
for example:
source kitchen-Album_3_2_19203733_0
destination kitchen-Album_3_2_19203733_0_leo_1.66
the album folder will still be ignored even after you changed the folder name of the already imported package to Album_3_2_19203733_0_leo_1.66.
just don't change/rename the blue part (original package name)
Click to expand...
Click to collapse
That's cool I guess... but it still seems like a lot to do, for such a simple operation as replacing a package with a newer one. I personally use beyond compare. It's a MUST have tool for chefs. It's great once you get to know how to use it.

NRGZ28 said:
That's cool I guess... but it still seems like a lot to do, for such a simple operation as replacing a package with a newer one. I personally use beyond compare. It's a MUST have tool for chefs. It's great once you get to know how to use it.
Click to expand...
Click to collapse
i bought beyondcompare too. it's a must have for chef's if you ask me too..
lot to do?? did you actually try the batch-file???
-adjust the 2 paths in the batch
-remove the lines you dont want to import (from the pop-up txt file - save and close to continue)
-adjust packages (insert lang subfolders and rename packages in the pop up temp folder)
-press any key (dos window) to move adjusted packages from temp folder to sub-folder "_NewPackages" in destination kitchen
for me, this batch is a real time-saver........
and i dont even have to use beyondcompare for this specific task anymore..
btw:
i will try to adjust the batch to show a pop-up of the destination-kitchen too when the temp folder is showing (so you dont have to open it manually to pick lang folders).

[solved] No Customisation + Welcome.exe [email protected]

Device flashes - Device boots - Device runs the Welcome.exe, but then no Customisation.
Iv recently added some EXT packages into my rom. i made them myself from .cab's with cab2ext. ive tested the .cab's before adding to my rom, they do work. but some programs that did work before adding the new EXT's now dont because of no customisation eg, Task Manager - the one on the today screen and also Windows Live. (iv only noticed these two at the moment but there will be more, to be honest i cant be arsed looking for programs that work or dont work when its quite obvious its because of no Customisation, if i fix that, they will work again.. simples )
Anyway...
I opened the new EXT packages ive added and checked all the files.. eg, .dat .reg and all "FILES" files, i even checked the .lnk's and all seems ok. i then checked them again.. yet everything still looks ok, but something is seriously f*cked!
Also another problem, a wierd one..
When i Soft-Reset/Restart the device, it boots up with the Welcome.exe again? (the Welcome.exe is meant to only run the once and then dissable )
Help? iv almost got my rom the way i want it - ive been working on this rom for 2months and i dont want to start building the rom from scratch...
..again! pmsl
Does anyone have any idea what is wrong, if this has happened to you, how did you fix it?
Thanks!
Rn

Check your runcc.lua, then the conf*.txt files you include in your rom, then all the commands you execute inside them.
One of these commands go wrong in your first boot and so you are stuck on customization.
If you use xda_uc or another user customization method, check those scripts as well.
It may happen, for example, if you try to install a cab and for some reason it fails.
If in your recent packages you overwrite one of your conf*.txt file, this could be the cause.
Ciao

...
cheers dude, thanks for your time and help, i think i understand what you meen..
[1)config*.txt <-- all config files are ok.]
[2)runcc <-- googled and i dont use]
[3)xda_uc <-- googled and i dont use]
raving_nanza said:
iv almost got my rom the way i want it - ive been working on this rom for 2months and i dont want to start building the rom from scratch.....again! pmsl
Click to expand...
Click to collapse
its ok claros, f*ck it dude, its the second time this problem has happened to me, it happened on my first rom too.. (2months ago.lol)
i litteraly started again from scratch (a nice clean slate) ill just start my rom again like i did then which will solve my problem.lol ive got all my programs and setting backed up (*in a messy folder of messy folders )
my new kitchen will basicly be up and running again by the end of the day, its my birthday on wednesday so i may as well set it as the rom date.lol
Raving_1337_Rom_V3 (Alpha)
Cheers anyway dude, muchly appreciated!
Rn
[changed title to solved, @claros]

raving_nanza said:
its ok claros, f*ck it dude, its the second time this problem has happened to me, it happened on my first rom too.. (2months ago.lol)
Click to expand...
Click to collapse
This happened to me at least 20 times, or more
Let's check together what happen at first boot, if I'm wrong anybody else will correct me.
1) files are moved from \windows to other directory according to your app.dat / initflashfiles.dat.
2) .provxml files are parsed to change config values or filesystem
3) welcome is executed, but this command don't stop startup so:
3a) autorun.exe or runcc is executed too to customize rom: these package runs according to the commands inside various config*.txt files in oem packages or sometimes in ext packages
4) user configuration, usually included as a call inside one of conf*.txt files is executed. If you don't use xda_uc, user customization should follow the same syntax as autorun/runcc
5) Last conf*.txt file should include at least a
LOCK: Disabled and a reset
At this point you should have completed the welcome wizard. If not, and your calibration data is not in registry, your are prompted again with welcome wizard at second boot.
Common errors during boot sequence are:
- wince.nls is missing
- app.dat / initflashfiles.dat error, such as creating subfolders inside non existent folders or statements not in unicode format
- registry / provxml errors during setup of welcome.exe itself, for example you disable the whole welcome wizard but don't write calibration data into registry
- chain error inside conf*.txt files, such as config.txt calls config_operator.txt which call config.txt, generating a loop
- a cab or command inside a config*.txt files cannot be installed, for example for lack of space or a missing certificate
What I usually do in these cases is:
- check platformrebuild log file for errors
- save my last tmp/dump folder to check what is really inside the rom and what is really overwritten by what
- If you can connect by activesync to device before reboot, explore the device itself, it's processes and registry
- recompile the rom putting semaphores inside app.reg files, .provxml files, config*.txt file. I usually add an ext package to be included as the last one (ZZZ_Claros_Fix) where I put a special app.reg, a .provxml and a modified copy of config.txt, config_operator.txt, config_end.txt etc etc.. If you don't have a diamond, you can boot without sdcard to avoid any sd_config.txt error
Starting a new kitchen from scratch for me is at least 20 days of work, I'd spend a day more finding a solution
Ciao

claros said:
This happened to me at least 20 times, or more
Click to expand...
Click to collapse
A Mortscript called Autorun.exe
V2 working again, Cheers!
*i started setting up a new kitchen then thought f*ck that!
Rn

Are you saying that you were cooking in mortscript, and the autorun.exe file from the mortscript package over-wrote the one from your OEM package? I think that happened to me once a while ago. I just left out the one from mortscript; I've never needed it before, anyway.

...
yeah a mortscript called Autorun.exe over-wrote my OEM Autorun.exe
i deleted it the mortscript, everythings sound now