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)?

Not newbie in taskbars but still weird things happen

I have made lots of taskbars but lately when i switched to dpi192 and searched for new taskbars to take some ideas and make my own i have some problems rather weird.
1)I downloaded some taskbars and opened them with WinCe cab manager.
In some of them their shellres dll appeared to be like the original one with the stock icons, but when i replace this file in my phone then the new icons appear.Where are these icons in the shellres? How is possible that restorator or reshacker doesnt show them?
2)I took the phcanoverbmp file of one of these taskbars and put my icons on it.It worked flawlessly with one build and when i changed build then the icons changed to the ones the phcanoverbmp had before i modified it.That means that in restorator I see my icons and in the phone I see the previous icons.Kind of magic!!
Well i checked in my kitchen that no other phcan or leophcan existed.
I would appreciate a reply on these questions!!

mmmm weird.. i had that issue with PE explorer once.... but then suddendly the XP screws up with a blue screen so i need to reformat and now the PE explorer and restorator shows me the changes
Edit: hope you arent playing with files from 6.5 into builds 6.5.X and viceversa cause it dont works

When you change build you must change again shellres.192.dll,shellres.192.dll.0409(or you native).mui.
Im not taskbar maker but this is what i can see in a taskbar cab that i downloaded.
I see also outres.192.dll,tapres.192.dll.
If you are a cooker i suggest you to put those files in an EXT package so for every new build you will not going to change them from SYS.
If you want only copy them into windows folder or make a cab i suggest you to sign them before or use sdkcerts.cab.
Here is a reg key to check:
Code:
[HKEY_LOCAL_MACHINE\security\ResOver\Bitmaps]
"BatteryIconLevels"=dword:00000065
"BatteryIconIdStart"=dword:000003E9
"FuncDll"="CDMA_RSSI_PPC.dll"
"BaseDll"="phcanOverbmp.dll"
"BaseId"=dword:00000000

Thank you guys for replying.
No i did not use wm 6.5 dll, It seems that somehow when you dont use a virgin dll and you overwrite the old icons with the new ones with restorator or reshacker, then sometimes the old icons remain and though you dont see them in the restorator they appear in the screen.
I made a progress,I used virgin dlls and this time signed them with the last msigner 2010.I made a cab and cooked as an external package using zzz as you said although this wasnt the problem.Now everything is fine, i can sleep.I dont know if it was the msigner version or the virgin dll.Ihave many times overwrighted icons, in already modified dlls, with restorator (without using virgin dlls) without problems.This time didnt work mayby.
Now the only problem i have is that when i check windows default in home screen then when i hit the windows button to go for example in start menu, then the x button doesnt return to titanium any more.
This doesnt really matters to me because i am an spb fun.I unchecked windows default which i do anyway and no problem.But maybe it should be nice to know why,maybe some other guys have the same problem.
Mmm, now the device stucked in boot screen once during sashimi, now i installed the programs manually, maybe I must fix this problem I previously described.
Any idea?
Thanks for your replies.

you must know that if you add in the kitchen a dll or whatever it doesnt matters if its signed or not... unless the tsk's with themes. cause the kitchen sign everything... the sign process of dlls or other thing are for patch working roms

+ Que PPC said:
you must know that if you add in the kitchen a dll or whatever it doesnt matters if its signed or not... unless the tsk's with themes. cause the kitchen sign everything... the sign process of dlls or other thing are for patch working roms
Click to expand...
Click to collapse
Thanks que ppc.

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.

*Request* 6.1 ESP (0C0A) Lang package

Hello there, im trying to make a 6.1 rom with ESP lang but i can't port the one posted by Da_G be cause the rom maker cab sends me problems with some files.
I hope some of you can help me with the lang porting or any pack I can use.
I'm using Old style kitchen made by aeroflyluby

Since you are speaking about WM 6.1 i suppose that you got the right build from the right Da_G thread....anyway ,here is the link:
http://forum.xda-developers.com/showthread.php?t=547314

Actually I'm using that package that you mentioned but no luck, when i change the files from the SYS folder the program "my build os" sends me an error anywhere and if y solve it (by deleting the problematic file) the rom maker (the .cab that calls the pack of tools) sends me an error while is rebuilding the files so I dont know what I'm doing wrong.
Do I have to use the SYS files with or without the 0409(ENG) files or i have to replace them?
Is there any proble if I cant find any 0C0A(ESP) OEM folder files?
I hope you can help me.
Regards.

If you are cooking for 0c0a then every 0409 folders must be left from your kitchen.
With 0c0a SYS you need 0c0a OEM at least OEM_Lang_0c0a otherwise your rom will not work.
Lokmetro said:
Actually I'm using that package that you mentioned but no luck, when i change the files from the SYS folder the program "my build os" sends me an error anywhere and if y solve it (by deleting the problematic file) the rom maker (the .cab that calls the pack of tools) sends me an error while is rebuilding the files so I dont know what I'm doing wrong.
Do I have to use the SYS files with or without the 0409(ENG) files or i have to replace them?
Is there any proble if I cant find any 0C0A(ESP) OEM folder files?
I hope you can help me.
Regards.
Click to expand...
Click to collapse

Oh i see. So i can extract 0c0a OEM files from any 6.0 dump folder? or I have to find a new oem folder files for 6.1?
BTW i'm cooking for a BenQ-e72 so I can't find any rom in spanish except for the one that came with my phone (WinMo 6.0)

a_GWM 6.0 OEM should be work with WM 6.1 at least you will need a WM 6.1 Initflashfile.dat (it is in OEM_Lang), sometimes Da_G shares his build within the Initflashfiles for every language,check in that thread to see otherwise try to cook it with your 6.0 initflashfile.dat and check if something is missing in StartMenu.
Lokmetro said:
Oh i see. So i can extract 0c0a OEM files from any 6.0 dump folder? or I have to find a new oem folder files for 6.1?
BTW i'm cooking for a BenQ-e72 so I can't find any rom in spanish except for the one that came with my phone (WinMo 6.0)
Click to expand...
Click to collapse

Thanks for the fast answer. I'm going to look for the WM from Da_G but I don't remember if i have seen that thread before, and btw I will take some time after I can post any advance be cause I'm not at home. for now I can only ask things if I have any question.

I have tried what you said but no luck. the phone wont start. it just stay in black screen, i don't know what i'm doing wrong

can you xplain exactly where does your rom stucks? maybe is not a SYS trouble maybe is a XIP trouble due to not pòrting ok or maybe is the wince. nls WWE or any SYS pkg missed

Well the rom wont give me any image, it just shows me a black screen and the normal screen lights for the rest it does nothing.
Once i got lucky but I had problems with the Start menu be cause i wasn't able to see the icons, i think it was caused by the initflashfiles.dat but now I can't do it again

[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