Guys,
does anyone know any information about the .provxml files that are run on Hard Resst that reside in the ROM?? ie what executes them etc...
AFAIK they generally contain registry settings and are executed by PreAutorun.txt or PreConfig.txt (can't remember the exact name) found on \windows\ dir.... watch for the lines starting with "XML:".
pof said:
AFAIK they generally contain registry settings and are executed by PreAutorun.txt or PreConfig.txt (can't remember the exact name) found on \windows\ dir.... watch for the lines starting with "XML:".
Click to expand...
Click to collapse
So, I assume this is where data connection details and the like are loaded?
richy240 said:
So, I assume this is where data connection details and the like are loaded?
Click to expand...
Click to collapse
no its not... data connection details are loaded from CAB files on the ExtROM... Operators use these .provxml files onto of the base rom they receive from HTC... these files are read on a Cold Boot (Hard Reset) and their settings entered into the registry...
but they probably could be used for operator settings.... but im in the process of writing an Operator Setting application for World Wide use....
Actually in the VPA ROM I'm working on, data connections ARE stored in the provxml files.
walshieau said:
no its not... data connection details are loaded from CAB files on the ExtROM... Operators use these .provxml files onto of the base rom they receive from HTC... these files are read on a Cold Boot (Hard Reset) and their settings entered into the registry...
but they probably could be used for operator settings.... but im in the process of writing an Operator Setting application for World Wide use....
Click to expand...
Click to collapse
on the cingular rom the data connection settings are set via xml and is stored in the rom, mms is set via cab, these are both NOT in the extended rom... was different than the wizard which had all the settings in the ext rom.
Connection Settings Are Stored In The XML Files On The Original Orange Rom And Are Executed By PreAutoRun.exe Reading Which Files To Execute From PreConfig.txt.
The Original Orange Rom Didn't Have An ExtRom And So Everything Had To Be Loaded From The Windows Directory.
Also Adding The Connection Settings XML To This File
"mxipcold_zzzbetaconfig_100.provxml"
And Then Cooking The File Into A Rom Will Install The XML Settings You Want At Startup And After Hard Reset.
Cheers
mousey_ said:
Connection Settings Are Stored In The XML Files On The Original Orange Rom And Are Executed By PreAutoRun.exe Reading Which Files To Execute From PreConfig.txt.
The Original Orange Rom Didn't Have An ExtRom And So Everything Had To Be Loaded From The Windows Directory.
Also Adding The Connection Settings XML To This File
"mxipcold_zzzbetaconfig_100.provxml"
And Then Cooking The File Into A Rom Will Install The XML Settings You Want At Startup And After Hard Reset.
Cheers
Click to expand...
Click to collapse
it all depends on how 'lazy' the operator feels hahaha... because the .provxml files are basically the same as the xml files... both used to configure your device with reg tweaks and operator settings... but.. i should have my Operator Settings app out this week finally
I have getting bunch of errors while trying to cook a ROM, during the last step of creating registry....I get the error and here is what the log says:
importing registry file ".\Registry\084c771d-5dd9-42b3-847c-7862312d8e9d.rgu"...
Failed to parse HKEY_CLASSES_ROOT\_wgt_opwidget\Shell\Open\Command!!!
InitRegistry FAILED in file ".\Registry\084c771d-5dd9-42b3-847c-7862312d8e9d.rgu" within a few lines of line 7.
ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\084c771d-5dd9-42b3-847c-7862312d8e9d.rgu"
wmain: (RGUComp) !ERROR failed building DEFAULT hives
Can someone more familiar with the process point me to the right direction so that I can fix this error.
basically I took the 405.1 ROM
Extracted it
Using the package tool, I created a few new packages using the cab files
Included them in the "C:\RaphaelKitchen\OEM" folder
Then when I try to cook, I put a check mark for the specific app that I added and click the Go button and that's when I get the error.
This specific error is related to the latest opera cab that I downloaded from this forum. I deleted the folder that was (under OEM) there with the shipped Opera was and replaced it with the one I created when I created packages.
Thanks (this is my first time trying to cook so this issue might be related to something basic I missed, just need some pointers)
Package Tool has a couple of known issues converting from cab to OEM's, most likely there are spaces or something in your file 084c771d-5dd9-42b3-847c-7862312d8e9d.rgu" within a few lines of line 7.
You'll need to open that .rgu in a text editor capable of supporting unicode.
thanks for the quick reply
sorry it was actually a newer version of Opera that was trying to replace before building, not GoogleMaps
here are the first few lines from the rgu, i am not sure what the issue is, the file looks pretty similar to other rgus that I have (for TomTom7)
Code:
REGEDIT4
[HKEY_CLASSES_ROOT\_wgt_opwidget\DefaultIcon]
@="\\Windows\\Opera9.exe,-162"
[HKEY_CLASSES_ROOT\_wgt_opwidget\Shell\Open\Command]
@="\\Windows\\OperaL.exe""" """%%1"
[HKEY_CLASSES_ROOT\.wgt]
@="_wgt_opwidget"
[HKEY_CURRENT_USER\ControlPanel\Keybd\ChangeBackVKeyCode]
"Opera_MainWndClass"=dword:00000008
[HKEY_LOCAL_MACHINE\Software\Opera\GSensor]
"IdleTime"=dword:000000c8
[HKEY_LOCAL_MACHINE\Software\Opera\Proxy]
"ProxyServerPort"="8080"
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Rai\:DEFBROWSER]
"0"="Opera Browser"
"1"="\\Windows\\OperaL.exe"
"2"=dword:00000001
"3"=dword:00000000
Is it possible to leave the cabs as is instead of converting them into OEM package then compile them into the ROM so that the cabs get installed at first bootup after the ROM is installed? (during customization)?
Where would I put the cabs in that case? under the "OEM\OperatorPkg" folder or somewhere else if that's even possible.
I see the problem, typical issue with package tool. does not handle escape characters properly..
Code:
@="\\Windows\\OperaL.exe""" """%%1"
should be:
@="\\Windows\\OperaL.exe \"%1\""
Also, yes you can put .cab's anywhere you like in \OEM (all gets mashed into one folder at the end, simply split up for convienience)
Just be sure to add a reference to that cab to config.txt or config_operator.txt or one of those config.txt's so the autorun routine runs it
Thanks for taking the time to help
I took the second option with keeping cabs and updated the config file
downloading apps to sign the cabs now.
cab won't install, just get copied over into windows folder
Thanks Da_G
I am having some issues trying to cook a cab into a rom, here is what I have done so far:
1) Extracted ROM
2) Created my certificate, added certificate as trusted root cert on PC
3) Signed cab with my certificate
4) Put the certificate in OEM
5) included the cab in OEM (sub folder within)
6) Included this entry in config_end.txt (CAB: \Windows\Fuze_Keyboard_Fix.cab)
7) Cooked ROM
8) Flashed
What I noticed was that during customization (after install) the Fuze_Keyboard_Fix.cab got copied over into the Windows directory on the Fuze but it was never executed/installed.
Is there something I am missing in the process?
I followed this link in order to create certificate and sign cabs, when I got the certificate cab created, I used the package tool to create OEM package of that cab and put the dsm, rgu files here (D:\RaphaelKitchen\OEM\mycert_cert) and the cert in OEM directory
I am not sure what went wrong:
1) either the certificate is not getting installed (I am not able to find the certificate in \Windows, but them again I am not even able to find oem.cert which should be there as well)
2) Or the issue is with the signed cab and that cab not getting installed properly.
3) Do I need to included the cab name in AAInfo.txt?
Thanks.
problem solved
I am posting a new reply in case anyone needs to use the above info to troubleshoot and fix similar issues
This is what I did to fix the issue:
Code:
1) Only pasted copy of the certificate into OEM
2) Went into "D:\RaphaelKitchen\OEM\OperatorPkg\mxipupdate_oemoperators_104.provxml" and appended the xml provisioning code that was created during generation of the certificate
3) Signed the cab and threw it into OEM folder
4) cooked & flashed.
My Fuze now had the keyboard and Name display fixed on Rogers network.
I will just have to sign new cabs and throw them in OEM and recook and flash in order to add other things.
Hi All,
with all of the kitchens found here, it is noticeable that when adding any packages to the OEM/SYS folders (i.e S2U2) then trying to re-build the rom specially in the process of BuildOS we got many errors that file already exist and then crashes.
after many research i got to know that the package will extract the files in windows folder for all packages on time then while installation, the files will be copied to the proper folders.
here is the problem, once trying to re-build the rom all files will be copied in the same folder.
is there a way to avoid this?
Hi robekia1,
Even I am facing the same problem when rebuilding os.
we will keep waiting for the seniors here to deliver a solution for us.
thanks to whom will help in this regard
I also faced this problem while cooking ROMs, Hey krazy! help please.
I guess, if we could know the file structure from the folder structue before installing, then it would be easy.
hmmmmmmmm, it seems that this problem have no solution as (Finding emulator for cooked ROM)
done the same and working
robekia1 said:
I guess, if we could know the file structure from the folder structue before installing, then it would be easy.
hmmmmmmmm, it seems that this problem have no solution as (Finding emulator for cooked ROM)
Click to expand...
Click to collapse
Hey I have done the same previously I love the s2u2 applications so I have cooked my rom with all 3 apps of s2u2 i.e. S2U2, S2P, S2V.
I created packages from package builder, then copied all files to one folder.
removing duplicates with latest one.
Also I changed the initflash file for the locations which is created by the package creator with the new folders path.
Then also I added the all item tag in XML to detect DSM files of the respective apps.
Make sure you have registry hack for installing third party apps in your ROM packages.
Enjoy... you will get all your S2U2 apps in your ROM.
Right now I dont have the folder I will upload it tomorrow if anyone wants.
Hope this information is useful to you all.....
Please Dooooooo
bhushangahire said:
Hey I have done the same previously I love the s2u2 applications so I have cooked my rom with all 3 apps of s2u2 i.e. S2U2, S2P, S2V.
I created packages from package builder, then copied all files to one folder.
removing duplicates with latest one.
Also I changed the initflash file for the locations which is created by the package creator with the new folders path.
Then also I added the all item tag in XML to detect DSM files of the respective apps.
Make sure you have registry hack for installing third party apps in your ROM packages.
Enjoy... you will get all your S2U2 apps in your ROM.
Right now I dont have the folder I will upload it tomorrow if anyone wants.
Hope this information is useful to you all.....
Click to expand...
Click to collapse
Thnx a ton budy for this information.
really, i can't wait till tomorrow for this folder because i want to see all these modifications whitch greatly will help all ppl here.
please upload it ASAP.
also, what about Cooked ROM emulation? i hope there is a solution up there whitch i'm not aware about.
registry hack
bhushangahire said:
Make sure you have registry hack for installing third party apps in your ROM packages.
Click to expand...
Click to collapse
What you mean by registry hack? it sounds something new for me.
do you mean any registry editor? or it is another OEM Package should be installed along with the ROM?
robekia1 right, all file will be in windows folder, if you put it in the "program files" folder, the files exist in windows folder too, that is will be wasto your phone storage. Avoid put in the program files folder will be increase your phone memory.
Usually the default directory of the CAB file is in the progam file, and if you use OEM creator to that CAB, it will copied to Program file folder and exist in windows folder, to make only in windows folderyou can use this method:
1. edit the initflashdat result of OEM creator, delete all value of program file, or
2. Before you use OEM creator, edit the installation directory of CAB file, use wincab manager to do it, or
3. use wincab manager to extarct the files in the CAB, and registry, after that you can make .rgu, dsm, shortcut, manually and input the shortcut location in the initflash.dat file (I always use this method).
Usually every CAB file have different files with other, and if the have same file it can be same with the SYS file or the author/maker of the CAb is same. you can choose the latest version of that file if it happend.
While cooking even though we separate files inside different packages, but at the time when imgfs.bin is created, all the files go to \Windows folder. Thats why there cant be two files with same name even when they are in different packages.
Now some apps have common dependencies. Like the DirectShow and mHubVO dlls are needed by Youtube, as well as streaming media. Now what happens is, if you take two packages for these, sometimes the author puts the dependency files in both the packages so that if someone uses one package and not the other, it still works. This mostly happens packages that are made by converting a cab to a package. So if you cook these packages, you need to make sure that they are not putting duplicate files.
The same thing also happens with also happens with registry settings. Somtimes, two or more packages update the same regisrty keys in their .rgu files. SO we need to take care of those too and remove the lines that dont apply to the version of files we are actually using in our kitchen. This is a necessary evil and thats why cooking is not a child's play.
Once a ROM is flashed, and phone boots for the first time, the initialization process takes place. Now the ROM cooks have two ways to initialize their packages : using the .provxml files, this works if you have newer OEM* folders like from Elfin or Opal, it basically requires the Autoshortcut.exe file as well as newer HTCUtil.dll. The other way is the older initflashfiles.txt files inside the packages.
The difference between two methods is that using initflashfile.txt you can only copy files and create folders on the file system, but provxml can be used to perform many different things like registry values, applying themes etc.
So using one of the methods you copy your files to appropriate locations. Do remember that this process if done wildly can decrease the availabel free phone memory noticeably. Thats why we sometimes go a bit furthur and do some programming stuff to minimize this. You people sometimes dont even notice what is happening behind the scene.
I tell you one such experience. Google maps is a package that copies all its files to \Program Files\GoogleMaps but i noticed if i dont copy the files by deleting the initflashfiles.txt, and run GoogleMaps.exe from \Windows, it runs just fine. This works in pro user's rom but in Manila ROMs, the Maps tab of Manila looks for GoogleMaps.exe in Program files folder. So i had a choice to either copy googlemaps.exe into program files folder and waste 2 MB of phone memory or loose the functionality of maps tab of manila.
What i did was the third way i thought of myself. I created a .NET application called GoogleMapsStub.exe and what it does is it runs the googlemaps.exe from windows folder and passes all the information to it that manilla passed to it while running it. This exe is copied into the \program files\GoogleMaps folder by using initflashfiles.txt as GoogleMaps.exe. So now manilla is happy that it has googlemaps.exe in its proper place and i am happy too coz the new exe is only 3.5 kb in size You can verify this in v3.1.1 of VanillaManila rom. Look in the program files folder you will get the 4 kb googlemaps.exe, put it on your pc and check its version in its properties, you will get my name there And if you check the windows folder, there will be a googlemaps.exe of 2 MB size and a GoogleMapsStub.exe of 4 kb size.
So sometimes hacks like these are necessary in order to make a perfect roms. ROM cooking is just like food cooking, It may appears to be like just putting the ingredients into a cooker and light up the gas stove and wait for the food to cook. But if you try that for first time, your food will not be eatable for sure It requires a careful balance of salt, pepper and other things to cook a tasty dish I hope i have made myself clear
Wonderful
AMAZINGGGGGGGGGGGG PPL
latest buildos/ visual kitchen has option to delete duplicate file while cooking but
i will make new kitchen in future (not soon) because current kitchen work fine for me and i have lots of other work like android + building to rom from weekly leaked sys of wp 6.5
Thanks ankit360 for the visualkitchen9.7, i'm already trying to use it but the problem is: the ROM generated by the kichen is not working for GENE.
i tried another kitchen for the same ROM and it still working fine, the only problem with it is the duplicate
bhushangahire, i'm still waiting for you to upload your files.
also, what about the reg hacker?
Hi Karzy,
" What i did was the third way i thought of myself. I created a .NET application called GoogleMapsStub.exe " you answered one of my query unknowingly, when I had extracted your ROM, I saw there was GogleMapsStub.exe which was not present in any other ROM I had extracted. So I was wondering what that file was about !!! Now I know what it was.
Thanks a lot karzy for sharing this info.
You have been always good in explaining things indetail, which helps a lot for new comers like me.
I m glad that i am able to help my buddies here.
find the files below...
robekia1 said:
bhushangahire, i'm still waiting for you to upload your files.
also, what about the reg hacker?
Click to expand...
Click to collapse
Please find the files below sorry for delay.....
S2U2 Application OEM folder.
S2APPS.7z (786.47 KB)
Registry Tweak OEM Folder.
Registry__Disable - Security warnings when installing non-certified application.7z (849 bytes)
Please find the link to ROM with S2U2 applications + Antivirus.
WM6.5_Old_21231.7z (51.91 MB)
bhushangahire said:
Please find the link to ROM with S2U2 applications + Antivirus.
WM6.5_Old_21231.7z (51.91 MB)
Click to expand...
Click to collapse
i guess this ROM is for OLD gene???Correct me if i'am wrong...
yup for old
htc3400 said:
i guess this ROM is for OLD gene???Correct me if i'am wrong...
Click to expand...
Click to collapse
yup you are right this rom is for Old ..
If anyone want it for new gene please ping here I will cook it for new also....
Thanks
bhushangahire said:
S2U2 Application OEM folder.
S2APPS.7z (786.47 KB)
Registry Tweak OEM Folder.
Registry__Disable - Security warnings when installing non-certified application.7z (849 bytes)
Please find the link to ROM with S2U2 applications + Antivirus.
WM6.5_Old_21231.7z (51.91 MB)
Click to expand...
Click to collapse
Thanks a Ton bhushangahire for sharing those links.
I appreciate this.
Now, i'm gonna read them character by character
I'm out of idea, any help appreciated!!!
When I'm trying to modify or delete any file inside the operator pkg, the default configuration for gprs internet is gone, modify the dsm file doesn't help.
The office 2010 cooked and installed from market place reacts differently, the cooked one when clicking word 2010 open up a blank docx document, needs to ok out and browse to template folder to choose template, but the installed opens up the template folder directly for you to choose doc or docx document. Is there a way to modify cooked one to reacts same as installed? import registry from installed one doesn't help, replacing installed files to kitchen doesn't help.
I cooking my own ROMS, but i would like to know if there is a way to change APN settings or change registry files before Building the ROM in oskitchen...
SO lets say i want to put a custom registry..So that after the ROM is flashed to the HD2 its already been applied instead of me having to wait for the ROM to be flashed then go in an manually put it in every single time i flash the rom.
yes you can, look for the package folder you are interested in,
example
C:\Kitchen\EXT\LEO\21869\LEO_External_Packages\AdobePDF_x.x.x
and there will be an app.reg or a 0775c01a-387c-4407-b51f-aff8596c3f17.rgu (numbers will be different, , ,just look for the .reg and/or .rgu files)
Those files hold the reg entries for that package, and you can edit them directly using something like ceregistryeditor.
Or,
bundle all your reg tweaks into a .cab file (with wince cab manager for example) and then use something like cab2ext to convert the cab into an EXT package for use in your kitchen. (Make sure it gets processed after the package it is altering.)
You can also do settings stuff with provxml, particularly for stuff like wifi passwords, email accounts, data connection settings, but i dont know how to make it instal them automatically. i just use the cab/ext or direct editing of the package.
I use makisu and manually provision the xml file for apn and email.