I searched the internet and this forum for quite a while but could not find anything specific.
I want to integrate some registry settings after cold boot via provxml. But I cannot figure out how they are applied after hard reset. If I put a new file into the (dump) rom, it will not be executed. I only read something about dsm-files or so...
any help out there?
cheerio.
chriskay said:
I searched the internet and this forum for quite a while but could not find anything specific.
I want to integrate some registry settings after cold boot via provxml. But I cannot figure out how they are applied after hard reset. If I put a new file into the (dump) rom, it will not be executed. I only read something about dsm-files or so...
any help out there?
cheerio.
Click to expand...
Click to collapse
As far as I know, the provxml has to be referred to in a *.dsm file.
What that means, is that you must create an OEM pack, and place your provxml files in that pack and generate the *.dsm file for that package...
To achieve this, I'd use ervius's package tool (you probably know this if you've done any messing around with packages!) and build DSM from here.
You'll need to create a new OEM pack (call it whatever you want, it really doesn't matter) and then put your provxml files in that folder before dragging that into the buildDSM exe, which will do all the hard work
thanks for your swift reply! sounds quite promising. will try it straight away. i hoped there would be an easy way like these tools.
cheers!
chriskay said:
thanks for your swift reply! sounds quite promising. will try it straight away. i hoped there would be an easy way like these tools.
cheers!
Click to expand...
Click to collapse
If that fails, you can rename the provxml file to *.xml, and reference it in your config.txt file for AutoRun.exe
e.g.
Code:
XML: \Windows\Provisioning.xml
ok, i did everything as stated. unfortunately, the newly created provxml was still not executed.
i use neokit (without package import) and just copied the provxml, the dsm and the rgu into the dump folder.
either there is more to that than just copying it, or i missed something when creating the dsm file.
any idea?
chriskay said:
ok, i did everything as stated. unfortunately, the newly created provxml was still not executed.
i use neokit (without package import) and just copied the provxml, the dsm and the rgu into the dump folder.
either there is more to that than just copying it, or i missed something when creating the dsm file.
any idea?
Click to expand...
Click to collapse
Ah... I think that's because of the way Neokit builds the ROM. I think you'll need to "import" the OEM pack, rather than simply copying the files (If that makes any sense...). Using an older version of neokit (I have the first release for OEM packs, and the latest release for everything else) you can import the packs and it works!
yeah, that is what i thought. could you provide me, please, with that older version? i have been looking for it all over the place without any luck.
thanks in advance!
chriskay said:
yeah, that is what i thought. could you provide me, please, with that older version? i have been looking for it all over the place without any luck.
thanks in advance!
Click to expand...
Click to collapse
Sure! I'll have to clear it out though...
Neokit original version is just being uploaded...
Done! Here: NEO.zip - 2.81 Mb
If inteks has any objection, I'll remove it...
i tried it and it worked like a charm! cheers, mate, for pushing me in the right direction!
cheerio!
chriskay said:
i tried it and it worked like a charm! cheers, mate, for pushing me in the right direction!
cheerio!
Click to expand...
Click to collapse
Glad that worked! I just wish Neokit still had the import OEM pack function!
Hi,
unfortunately I am not able to implement a new *provxml to a new ROM.
I know http://forum.xda-developers.com/showthread.php?t=398025
and some other threads, but all my entries (Mailaccounts, WiFi informations - which I got with rapiconfig) are not in my new ROM.
I am doing somewhere a mistake. It does not work:
I have done the following:
1. created an acconts.provxml
2. renamed to _setup.xml
3. Created an OEM package with Ervius Package Creator.
Have now 5 files in the OEM folder: _setup.xml, *.rgu, *.dsm (size 0k), option.xml and initflashfiles.txt
4. Moved option.xml out of the OEM folder
5. Drag and drop OEM folder over BuildDSM.exe. This creates a new *dsm (size 1k)
6. place back option.xml in OEM folder
7. copy OEM folder under \Packages - i have tested also the OEM folder
8. cooked and burned ROM
Any help is welcome.
Regards
kuzco1
kuzco1 said:
Hi,
unfortunately I am not able to implement a new *provxml to a new ROM.
I know http://forum.xda-developers.com/showthread.php?t=398025
and some other threads, but all my entries (Mailaccounts, WiFi informations - which I got with rapiconfig) are not in my new ROM.
I am doing somewhere a mistake. It does not work:
I have done the following:
1. created an acconts.provxml
2. renamed to _setup.xml
3. Created an OEM package with Ervius Package Creator.
Have now 5 files in the OEM folder: _setup.xml, *.rgu, *.dsm (size 0k), option.xml and initflashfiles.txt
4. Moved option.xml out of the OEM folder
5. Drag and drop OEM folder over BuildDSM.exe. This creates a new *dsm (size 1k)
6. place back option.xml in OEM folder
7. copy OEM folder under \Packages - i have tested also the OEM folder
8. cooked and burned ROM
Any help is welcome.
Regards
kuzco1
Click to expand...
Click to collapse
Don't rename it to setup.xml. Leave it as a provxml file.
l3v5y said:
Don't rename it to setup.xml. Leave it as a provxml file.
Click to expand...
Click to collapse
Thanks for this tip, but it does not work in my case. I have still no email-accounts after cooking my ROM.
If I "import" my accounts.provxml with "rapiconfig /p accounts.provxml" everything is fine.
BuildosX-log.txt does not say any error.
It is necessary to put my OEM folder under a special directory ?
I have tested \packages and \OEM.
Regards
kuzco1
kuzco1 said:
Thanks for this tip, but it does not work in my case. I have still no email-accounts after cooking my ROM.
If I "import" my accounts.provxml with "rapiconfig /p accounts.provxml" everything is fine.
BuildosX-log.txt does not say any error.
It is necessary to put my OEM folder under a special directory ?
I have tested \packages and \OEM.
Regards
kuzco1
Click to expand...
Click to collapse
Should be put in \OEM.
You could try using SDAutoRun as an alternative.
Try the attached OEM pack (obviously with your details added back in...)
Related
Hello everybody!
Even if this is my first post on this forum, I use to visit this useful place since years, I tried many of those great WM6 ROMs made by our ROM cookers (thanks to all), then I tried to cook my own ROMs using tools recommanded in the Wiki.
But those kitchen tools weren't conveignent for my use, it was a lot of work and patience for making ROMs, we need to use many different programs and scripts, and I thought that the cooking process could be really simplified using an unified graphical interface like dutty's tool. I was patiently waiting for his Hermes Rom Koch V2, but finally I started to develop my own kitchen tool!
Here are some features of this program:
- ROM file manager (to add/delete/extract files or to create shortcuts)
- ROM layout editor (to edit init flash files)
- Registry editor (to modify/import/export default & user registry)
- CAB install files integration
- ROM creation from original OS image or dump directory
I posted some screenshots for better explanations.
This program simply use aWaiter and ImgFS tools for ROM creation/extraction.
For now I still have a lot of work on it, but I would like some advises from experienced developers on this forum, because even if my program works, I would like to know if the cooking process is porper and safe, and how I could improve it (for example using internal functions for ROM creation/extraction instead of external programs, implementing NBH tools,...).
If some of our XDA-developers are interested, I would really like to make this project an Open Source "all-in-one" ROM cooking program, gathering all the others kitchen tools in an unified graphical interface offering the easiest way to cook nice ROMs for our Hermes and certainly for other devices.
I know that I didn't give many details about my program but don't hesitate to ask me about it. I would also have few questions for developers.
Developers and ROM cookers, I'm waiting for your feedback!
Thanks.
This looks very user friendly, I will be watching closely. Good work.
What language is it in? (programming language that is)
Midget_1990 said:
What language is it in? (programming language that is)
Click to expand...
Click to collapse
I developed this program in C# (using .NET framework 2.0).
Thx for your work! It would be better if the tool support packages.
http://forum.xda-developers.com/showthread.php?t=296861
Where to download??
Thanks for the link. I already thought about working with packages because it seems to be a better way to make "clean" ROMs, but I couldn't find enough information about how to extract/build packages in ROM.
I tried bepe's package tool on my own cooked ROM and I noticed that removed files were marked as missing in packages, and all the files I added weren't moved from dump directory. There is nothing surprising, but I wondered if adding/deleting manually files from ROM, causing "corrupted packages", can have any effect on final ROM. If not then why packaging information (like .dsm and .rgu files) are still present in ROM after all packages were merged? What exactly contains .dsm files, and how to create them for adding new packages?
Could someone tell me more about building packages, or tell me where I could find all the information I need.
Thanks
I'm still working in this project, so I didn't plan any release yet.
Good idea and nice project.
Go on dude !
Good work.
Great work so far - I fullly support this project.
Lookign forward to the release.
schaps said:
Could someone tell me more about building packages, or tell me where I could find all the information I need.
Click to expand...
Click to collapse
Great project - and I agree, it definitely should support packages. If you've had a look at bepe's kitchen, you already know how much easier it is to understand the purpose of all the files in a ROM if they are organized in packages.
.rgu files are Registry "source code". They are not part of the package mechanism. And yes, when cooking a ROM you can leave them out, as they are not needed at run time. Saves a bit of space.
The .dsm files, otoh, are needed at run time.
When I cooked my ROM, I did find some information (written by bepe) here in the forum about how to make your own packages. Can't remember where that was, but I found it on my hard disk, so I simply quote it here again:
How-To build ur own OEM Package:
An OEM Package is just a simple folder containing files and registry settings for the ROM
First of all you'll need a GUID number for your Package.
Go to http://www.famkruithof.net/uuid/uuidgen to get one.
In my case:
283b9db7-cb03-4c1b-820e-ca49b2c3b5db
Necessary steps:
1. Create a new folder:
Dev/OEM/[Your package name]/
2. Create a empty text file:
Dev/OEM/[Your package name]/283b9db7-cb03-4c1b-820e-ca49b2c3b5db.dsm
(CreateOS.exe will finish this file for you)
If needed:
3. Create an UNICODE text file:
Dev/OEM/[Your package name]/283b9db7-cb03-4c1b-820e-ca49b2c3b5db.rgu
This file could be used to add registry entries to the ROM
First line is:
REGEDIT4
...
and there MUST be a empty line at the end!!
4. Create an UNICODE text file:
Dev/OEM/[Your package name]/initflashfiles.txt
This file could be used to create folders or copy files, shortcut on the ROM.
For Example/ Ilustration: Open or read Dev/LOC/initflashfiles.dat using a text editor or any premake initflashfiles.txt at one of the OEM folder.
and there MUST be a empty line at the end of iniflashfiles.txt also!!
Copy all files you need to Dev/OEM/[Your package name]/
Click to expand...
Click to collapse
Hope that helps. If I remember correctly, bepe told me that the OEM folder is treated a bit differently from the SYS folder, so it might be you can't create packages there. But then, you probably also shouldn't.
Oh, and about the initflashfiles.dat: you are aware that the initflashfiles.dat just copies files and does not move them? Using this feature extensively uses up ROM space very quickly, so it should be done for small files (like the start menu shortcut files) only.
Cheers
tadzio
Thanks a lot for your help tadzio!
I also read the different steps about how to add a new OEM package, I found information on this Wiki if someone is interested : http://wiki.ppcgeeks.com/index.php?title=Kitchen.
I think I know enough about it but what I would know is how to extract packages then to merge them for creating a ROM image, like do bepe's tools?
I confirm I also heard that OEM folder processing is different from SYS folder.
Concerning the initflashfiles.dat I guessed that files were copied from ROM to storage memory, good to have a confirmation. So it means that if we want to include a new program in ROM, we should better to let it in Windows folder than to put it in a Program Files folder, right? I have another question about initflashfiles.dat, I saw that it sometimes uses variables for directories instead of strings (for example Directory(LOC_XXX), Directory(0409_XXX),...), where could I find those variable declarations?
schaps for president
schaps said:
Thanks for the link. I already thought about working with packages because it seems to be a better way to make "clean" ROMs, but I couldn't find enough information about how to extract/build packages in ROM.
I tried bepe's package tool on my own cooked ROM and I noticed that removed files were marked as missing in packages, and all the files I added weren't moved from dump directory. There is nothing surprising, but I wondered if adding/deleting manually files from ROM, causing "corrupted packages", can have any effect on final ROM. If not then why packaging information (like .dsm and .rgu files) are still present in ROM after all packages were merged? What exactly contains .dsm files, and how to create them for adding new packages?
Could someone tell me more about building packages, or tell me where I could find all the information I need.
Thanks
Click to expand...
Click to collapse
Hi Schaps,
you can have a look in this link:
http://forum.xda-developers.com/showthread.php?t=312985
it's a tool to re-build DSM file, which is better than just creat an empty .dsm file when making new package.
hope this help. It will be cool if your new tool support package.
Hey Guys,
Yet another sleeples night, looking at something that is probably simple and getting no where.
THE PROBLEM:
APPARENTLY you can change a CAB file into an OEM so that it can be used in Pandora Kitchen, the kitchen thread says its possible, but doesnt really give directions as to how.
Considering this is a new thing to, and there is no info about this on the site (that i can find)
Can someone please tell me step by step how to do this, and by step by step i mean:
1).................
2).................
3).................
4).................
etc etc
Thankyou for your help in advance
Here is a test package I made, but I keep getting a registry errors. Maybe someone can tell me what im doing wrong. I think it was better to keep all this in the kitchen thread personalley but as long as I can figure this out I dont really care.
Extract this file and take the "Remote Desktop" dir and drop it in the OEM dir in the Kitchen, and it shows up and all but when you go to build with teh green arrow I get a registry compiling error.
I also attached the original cab file that I started with when attempting to create this package.
Also attached is the cab manager that Matt uploaded, I am sure its the same as the one posted above but this has a readme and what not.
First Matt told me this:
Using this tool (many out there, this one's free and does a good job), extract the cab to a folder, then click on XML and grab the .rgu contents. Be wary of the format, as you have to delete any spaces between entries, such as "biteme" = dword : 00000001 should read "biteme"=dword:00000001.
Also, ensure that any path in this file (file system, not registry) is in this format: "\\Windows\\Startup" The second slash is required. Also, remove any references like %ce%\Windows, just change it to "\\Windows". You'll get the idea. If it ain't right, BuildOS will fail while creating the registry.
Move all the files into the top level in the folder you made, and remove all the extra crap like the inf file, and sometimes there's an xml file there too - note that you may need to convert to a provxml if the settings in it are required.
Use this site http://www.famkruithof.net/uuid/uuidgen (verion 4) to get a new GUID. I'd suggest coping a .rgu and options.xml file from another package since the file has to originate a certain way - and only use notepad to edit.
Just follow the example in the other packages - you'll find just about every way to do things in there.
As far as more details on using the program, just play with it. It's pretty simple
Then Bennec83 told me this:
what exactly are you trying to do? extract a CAB? if you are, using the file i uploaded earlier:
1)Launch CAB Manager.exe
2)on main screen extract CAB to a folder
3)click on the XML tab in top bar of the main window of CAB Manager.exe
4)in the window that opens, select Registry Keys
5)copy everything from the screen into WORDPAD
6)remove all the spaces
7)save the file as "UNICODE", once saved change the extension to somename.rgu
if you are trying to add an OEM to this kitchen i dont think you can just add them, please correct me if im wrong.
i hope this helps, if not tel me abit more about wat u want to do n ill try to help abit more!!
I understand the INF file as well, I just dont know how to add multiple directories as the destinations for a package, when a cab inf will tell you where there all suppost to go.
--Update--
I removed the NON-WORKING package, as it is now obsolete, see post below I got it working.
Ok then I understand the logic, and then the proper elaborated instructions can be pasted at the first or second topic of the Kitchen thread.
So I guess im doing something wrong with the reg, I have tried it a bunch of diffrent ways by comparing it to existing packages but I still cant seem to get it.
This quote by matt is what leads me to believe that.
Also, ensure that any path in this file (file system, not registry) is in this format: "\\Windows\\Startup" The second slash is required. Also, remove any references like %ce%\Windows, just change it to "\\Windows". You'll get the idea. If it ain't right, BuildOS will fail while creating the registry.
Ok I did it, I was reading an old post of bepe's and he said "add the reg to the end of the file (and the last line must be empty)" and so I hit enter and left the last line blank and BAM it worked so here is my first package contribution.
Maybe you can start adding these to the first post and we can start to make a collection for matt to add and test with his kitchen ?
Here is another one HTCustom 1.7 ready to go package for the kitchen
Damned if I can work it out!
Can anyone please package any of the following cabs?
Ive added JUVS HTC Home because the one included in the kitchen has the coloured icons not the original b&w.
Many many thanks in advance
I am still not able to completly figure out how to make a package where you must put files in diffrent locations other then the windows folder ? I would veyr much like to figure this part out.
I dont think he's having a go at you - he's just as frustrated as you and I with this. I would love to be cooking my own roms and with the wonderful pandoras kitchen I am getting alot further along but I guess I got a lot further to go!
well, by searching you can find how to do this!!!
click on this ftp://xda:[email protected]/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf
this pdf file got what you need!!
under "Making a Package from a CAB file"
Look here bennec83, the comment i made was not meant to be a flame at all. If anything, it should have helped you alot with what you were trying to accomplish with the program and, making packages. I mean how much more direct can i be with helping you? As I said to you before, yes some of the chef can be a little vague with explaining the "How To's" of cooking or anything else, but that still didnt stop my progression of learning what i wanted to learn on here. What i explained in the CORE's Kitchen thread, was basically 80% self taught thru reading post & threads on xda, google searching, and trial and error. The other 20% was thru xda forum members input. I have a basic understainding of computers with no type of programming skills, and yet still, i was able to grasp the concept of cooking roms and making packages. Yes sometimes you have to put 2 and 2 together to figure things out on here. How I did it was I looked inside CORE's additional OEM packages and noticed that the files inside all the oem were extracted into the root of the folder's Dir...ok..so I would assume that you spent considerable amount of time trying to figure out that OEM package program(inside CORE's Kitchen its called Cab Analizer), then i would assume that you know that it extracts files within a .cab...ok... with that given....if you look back into an already made OEM package and many others, you'll notice that most ,if not all, carry an "initflashfile.txt"(which i figured out the correct data input) and many packages also carry .rgu & dsm files, so guess what....you need to find out what are .rgu & .dsm files, and there functions(if know no ones whats to tell you in a timely manor then, search or google, like i did!) Once you learn about those then, you'll notice that the OEM package program you have infront of give information about the reg keys of the cab (if available), then you start putting 2 & 2 together! You mention in your quotes that the programs sucks ass, well that program is a key part in making packages, If you can find a better one, please let me know!
NightmarE said:
well, by searching you can find how to do this!!!
click on this ftp://xda:[email protected]/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf
this pdf file got what you need!!
under "Making a Package from a CAB file"
Click to expand...
Click to collapse
thankyou so much for this, i actually know what to do now i really appreciate this. you dnt know how much!!!
thanks alot
chrisnash said:
I dont think he's having a go at you - he's just as frustrated as you and I with this. I would love to be cooking my own roms and with the wonderful pandoras kitchen I am getting alot further along but I guess I got a lot further to go!
Click to expand...
Click to collapse
you are right that wasnt flamage!! i have been lookin so long in this forum i totally didnt think the answer would be in the wizard forum.
i have read and understood the instreuctions here:
ftp://ftp.xda-developers.com/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf
i just wish i cud have found it earlier
perhaps I'm an utter fool, but I'd like some clarification from those of you who understand this, mind you I do have Faria's PDF:
1) For a .cab with purely registration files (ie, the Cingular WAP Settings) that contains a .inf when extracted, all I would need is the .rgu to put into BuildOS, right?
2) The .dsm file (and iniflashfiles) are only needed if the .cab is an actual application, and the .dsm file that you create can very well be empty (from what I understand from Faria's rom).
Maybe it's a lack of sleep, but I'm just not getting my head around this and am so far using the Install Cabs feature from HTCustom 1.7 after flashing.
I was trying to do the cignular settings and It seemed to me that all those reg entries appear like blank er something was wrong with them, I could be wrong but thats what it appeared like to me.
Bennec, ok then bro, my mistake, I guess I shouldnt of assumed that post was directed towards me, it just felt that way and I know you were frustrated.
Lets make this the best CAB to OEM Package thread ever and start a collection on the first post, also with all you have learned now, have you figured out a way to make a package with a cab like opera where the files must be placed in to diffrent dirs ?
where are you all stuck at?
to move files to a different directory you need to use initflashes. Keep in mind that this copies it to a different directory not actually moves it. The original file will still be in \\windows
If all you want is to add registry entries, add them to an existing packages registry entries. If you create a new package for the registy entries it should have a dsm file as well.
If you want the check box in buildos you will need to create an option.xml file as well.
bennec83 said:
you are right that wasnt flamage!! i have been lookin so long in this forum i totally didnt think the answer would be in the wizard forum.
i have read and understood the instreuctions here:
ftp://ftp.xda-developers.com/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf
i just wish i cud have found it earlier
Click to expand...
Click to collapse
I'm glad you found the info you need, and are on your way to making progress. I apologize for not being able to assist more than I did, but I've got my hands full getting v3 ready for release.
Good luck and happy packaging!
NYD - long time, no see!
goto the CORE's kitchen thread. Read my posts and familiarize urself with a program called "compare it". Use this program to compare ur registry when the app is freshly installed, to the registry without the app installed, and pull the reg keys that way!
mattk_r said:
I'm glad you found the info you need, and are on your way to making progress. I apologize for not being able to assist more than I did, but I've got my hands full getting v3 ready for release.
Good luck and happy packaging!
NYD - long time, no see!
Click to expand...
Click to collapse
I understand you have lots to do on your kitchen, congrats BTW!! amazing kitchen, how is touch flo goin?
notyourdaddy said:
where are you all stuck at?
to move files to a different directory you need to use initflashes. Keep in mind that this copies it to a different directory not actually moves it. The original file will still be in \\windows
Click to expand...
Click to collapse
Hmmmmmm.
So its not possible to cook a Rom with custom apps in Progam Files only? I mean if they are always in \\windows too then its better to install the files than to cook it in the rom.
I have always believed you should add as little as possible to Rom:
From Tadzio's 'Want more Storage' Thread.
tadzio said:
...clip...
I modified mamaich's ImgfsTools so that they now create the smallest possible OS.nb from a 'dump' directory, and also write the partition table and MSFLSH header matching the new size.
...clip... make a ROM as small as at all possible, removing anything that users may not want, and turn every removed feature into a .cab that users can install to Storage...clip...
Cheers
Daniel
...clip...
Click to expand...
Click to collapse
I am looking to create some cabs (now that I have WinCE figured out) and wondered if others had quick ways of getting all of the reg keys exported for specific applications so I can add those into my cab.
If I can get buttons, today screen prefs, apps, and a few other things done in one compiled "Setup CAB" I will have my phone auto-customized I had it before flashing. I am so close to having only cabs in my UC if I can get this, and do away with the copy commands.
serfboreds said:
I am looking to create some cabs (now that I have WinCE figured out) and wondered if others had quick ways of getting all of the reg keys exported for specific applications so I can add those into my cab.
If I can get buttons, today screen prefs, apps, and a few other things done in one compiled "Setup CAB" I will have my phone auto-customized I had it before flashing. I am so close to having only cabs in my UC if I can get this, and do away with the copy commands.
Click to expand...
Click to collapse
This is actually something I've been wondering about and kinda 'working on'.
I'm trying to find out how certain applications store registration info (registry, files, etc.)
Just a few in question that I'm trying to auto-register on flash:
Resco Tools: Backup and Explorer
Handmark Games (Yahtzee and Scrabble)
serfboreds said:
I am looking to create some cabs (now that I have WinCE figured out) and wondered if others had quick ways of getting all of the reg keys exported for specific applications so I can add those into my cab.
If I can get buttons, today screen prefs, apps, and a few other things done in one compiled "Setup CAB" I will have my phone auto-customized I had it before flashing. I am so close to having only cabs in my UC if I can get this, and do away with the copy commands.
Click to expand...
Click to collapse
It's simple. If you bought WinCE you will then be able to use the option to export and import REG Keys.
So all you would need to do is open a CAB from any program -- Export the REG -- and close it out.
Then open the CAB project you made and import the REG key and your good.
But you must first buy WinCE. The evaluation copy doesn't let you do this. Well it didn't let me.
For cabs that are just changing reg keys for you and not actually installing anything...it's easier to just create an xml file. Name the xml file _setup.xml and use makecab from the command line like this:
Code:
makecab _setup.xml yourcab.cab
CeREgistryEditor also makes cabs from registry files. Free program.
studentjunk said:
CeREgistryEditor also makes cabs from registry files. Free program.
Click to expand...
Click to collapse
The two aspects i was looking for are solved by this program and GC's suggestion. Thanks!
studentjunk said:
CeREgistryEditor also makes cabs from registry files. Free program.
Click to expand...
Click to collapse
So, I need to give a little more explanation for my question.
I am pretty sure that I know how to change registry keys one by one using XML.
I am not sure if it is possible to export everything from a folder in a way that it can be combined with other registry exports and ultimately cabbed. Say I am looking to replace every key in HKLM/Software/Microsoft/Today after a new flash so that certain things are enabled and disabled.
My hope is that I will be able to export the entire "today" in such a way that I can add those to a wince cab. It would be nice to be able to export several of these "folders" at one time and drag them over.
Like I said, I am trying to prevent having to do this one key at a time so that in the future even if I change the setup I don't have to change the strategy for export/import.
So, I need to give a little more explanation for my question.
I am pretty sure that I know how to change registry keys one by one using XML.
I am not sure if it is possible to export everything from a folder in a way that it can be combined with other registry exports and ultimately cabbed. Say I am looking to replace every key in HKLM/Software/Microsoft/Today after a new flash so that certain things are enabled and disabled.
My hope is that I will be able to export the entire "today" in such a way that I can add those to a wince cab. It would be nice to be able to export several of these "folders" at one time and drag them over.
Like I said, I am trying to prevent having to do this one key at a time so that in the future even if I change the setup I don't have to change the strategy for export/import.
Click to expand...
Click to collapse
Read my email and take a look at the registry cab I attached.
gc14 said:
Read my email and take a look at the registry cab I attached.
Click to expand...
Click to collapse
Thanks GC, this is what I needed.
Final XML
Here is my final XML for anyone who cares to share theirs, I learned a lot by looking at GC's (credit where it is due). I put my sdconfig.txt on here too.
Feel free to let me know if there is a better way to do any of this. I will be testing tonight to see how it does after a flash. This should save me 20 minutes of tinkering if everything goes right.
Other than the background not being possible (that seems hard to believe there is no way to do this), I will only have a few things to set up when flashing if all goes well. This will be so worth the hour time it took to create.
Any way to register devices via XML (wifi, bluetooth)?
PS. Though I didn't do it here, I have cabbed the _setup.xml file for installation with UC.
All those CPY commands are still unnecessary. You could make one cab to do all of that very easily.
Also, why do you have LOCK/HIDE commands around the reg cab?
gc14 said:
All those CPY commands are still unnecessary. You could make one cab to do all of that very easily.
Also, why do you have LOCK/HIDE commands around the reg cab?
Click to expand...
Click to collapse
Got those two things cleared up, cabbed the files to copy which works great.
Can't seem to figure two things out:
1. xml didn't install registry keys. Did I miss some setting in WinCE (I just set it as universal, added to files, and set the location to %InstallDir%). I had all of the files I was going to copy in UC in this same created cab as _setup.xml; the copied files went across fine, but no registry keys were changed. This leads me to believe that xml didn't load correctly or at all.
2. Copying folders. I cant seem to copy folders directly into WinCE so I would think that the folder must be created then the files must be copied across. How do you create these folders (I want to copy across AstroGPSLauncher and HTC Home icons to root). I tried using the copy command in UC as well but I think the syntax was wrong by using backslash after folder name in CPY1 and no slash after new folder in CPY2.
Thanks, I am so close to getting this.
Got those two things cleared up, cabbed the files to copy which works great.
Can't seem to figure two things out:
1. xml didn't install registry keys. Did I miss some setting in WinCE (I just set it as universal, added to files, and set the location to %InstallDir%). I had all of the files I was going to copy in UC in this same created cab as _setup.xml; the copied files went across fine, but no registry keys were changed. This leads me to believe that xml didn't load correctly or at all.
2. Copying folders. I cant seem to copy folders directly into WinCE so I would think that the folder must be created then the files must be copied across. How do you create these folders (I want to copy across AstroGPSLauncher and HTC Home icons to root). I tried using the copy command in UC as well but I think the syntax was wrong by using backslash after folder name in CPY1 and no slash after new folder in CPY2.
Thanks, I am so close to getting this.
Click to expand...
Click to collapse
1. You don't use WinCE to create cabs from provxml. You use makecab as I previously stated.
2. Get rid of the CPY commands, don't use them at all. If you want to install youricon.png to root, you just add youricon.png as a file in the cab and set the location to root. Default install directory doesn't matter, you can specify install location for each file separately.
gc14 said:
1. You don't use WinCE to create cabs from provxml. You use makecab as I previously stated.
2. Get rid of the CPY commands, don't use them at all. If you want to install youricon.png to root, you just add youricon.png as a file in the cab and set the location to root. Default install directory doesn't matter, you can specify install location for each file separately.
Click to expand...
Click to collapse
So, makecab worked to create the cab but it states that the installation of the cab was unsuccessful. Here is the zip of the setup file and the cab I created (I kept yourcab.cab naming for fun).
P.S. I got rid of all copy commands, but still can't figure out how to create a new folder on the device using xml or wince. Please explain how I can cab a folder with all its contents, or create a new folder in xml, then UC a cab to install the contents.
That version of WinCE doesn't allow for import of complete folders. Later versions do.
You can also try QuickCab. Don't remember the user's name, but it is being developed by an XDA member. I believe it allows for copying complete folders, and has a simple GUI.
Edit: If you are just looking to do it for AstroGPS it should be fairly easy. Isn't it just one or two files in /AstroGPS... and a shortcut in /windows/start menu/programs? If so, just drag the file (or two) into WinCE, and it will ask you where you want it to be installed. Then just choose /AstroGPSLauncher (you have to create a new folder, but the option is right there).
bedoig said:
That version of WinCE doesn't allow for import of complete folders. Later versions do.
You can also try QuickCab. Don't remember the user's name, but it is being developed by an XDA member. I believe it allows for copying complete folders, and has a simple GUI.
Edit: If you are just looking to do it for AstroGPS it should be fairly easy. Isn't it just one or two files in /AstroGPS... and a shortcut in /windows/start menu/programs?
Click to expand...
Click to collapse
Thanks for looking into the second issue.
Right, but I need to have that in a folder called AstroGPSLauncher on the root. I also am looking to install the HTC Home folder (overwrite the other one). I will get a newer copy of WinCE.
Anyone have any idea why this cab won't install?
serfboreds said:
Other than the background not being possible (that seems hard to believe there is no way to do this)...
Click to expand...
Click to collapse
Are you talking about your Today screen background? You are basically looking to have a certain theme selected? If so, then that is no problem. TSK's are basically just cabs themselves. The Theme selection app in WM just reads the TSK, imports the registry color info, and copies tdywater.gif/.jpg and stwater.gif/.jpg to /windows. At startup, WM reads those image files and assigns them as your Today and Start Menu wallpapers. Just use WinCE to export the contents of the TSK. Then use whatever method you like to update your registry and copy those files to /windows.
serfboreds said:
Any way to register devices via XML (wifi, bluetooth)?
Click to expand...
Click to collapse
I'd like to know this as well. I might look into it, but please let me know if you find a solution. Thanks!
Serf, do you have AIM? If so pm me your sn so we can talk over that. This is a really really simple process, and I know exactly why the cab isn't installing, but it sucks to explain over forums/email.
gc14 said:
Serf, do you have AIM? If so pm me your sn so we can talk over that. This is a really really simple process, but sucks to explain over forums/email.
Click to expand...
Click to collapse
serfboreds7777 and I am online now.
I have this mostly figured out for my needs, a few tweaks and some new ideas since getting things flashed with UC / XML / Cabbed files. If anyone wants to get some help setting up their xml and UC I will do my best to help you through the process.
Props to GC, the man knows his stuff.
Okay trying to cook my first ROM, but I have some apps that I always seem to need to install after I change my ROM. How can I add these to my ROM?
The programs are Remote Desktop (Finster's CAB file), BackGammon (exe taken from another PDA), Logmein (CAB file), Advanced Config 3.3 (and NetFrame 3.5), plus some other games I have gathered over the years.
Can anyone assist? I have looked at the OEM directories from OEM 5.5, but there are no CAB files and the other files I can't see how to create.
Anyway - any assistance for a total noob would be appreciated.
DT
From the Nike kitchen, tools>package creator. Copy your cab there, and then run package creator and select the cab. A full package will be created for you to add to your OEM folder.
THanks for that, what about the exe files that just need to be placed in a folder and a shortcut created - eg the backgammon game from the other PDA?
Also - just checking - I open the can and then extract it to create the package?
Thanks
DT
d_train said:
THanks for that, what about the exe files that just need to be placed in a folder and a shortcut created - eg the backgammon game from the other PDA?
Click to expand...
Click to collapse
Probably easier to do one manually or modify another package to suit. If you look in a package:
1) option.xml gives the tickbox for you to include or exclude in cooked ROM.
2) ****.dsm is a 'time stamp' of order of processing of the package.
3) ****.rgu are registry entries that you can change to configure the program.
4) initflash.txt gives the location for files to be copied to - directories, links, folders etc.
5) ****.provxml is an alternative to using .dsm and .rgu.
Also - just checking - I open the can and then extract it to create the package?
Click to expand...
Click to collapse
Just click on open cab, select the cab, and wait for the okay. The package is ready for use.
Thanks for the info - tried the manual way copying some of the info from other packages. I get an error - "Error building default.hv and user.hv!" when I try the first step in creating the ROM. Without the backgammon program selected this step goes fine.
Here is the info I used...
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<Items>
<Item name="Backgammon" group="Programs" checked="true">
<Tip></Tip>
<Guid type="p">f70211a0-0b0a-11de-8c30-0800200c9a66</Guid>
</Item>
</Items>
and...
;-------------------------------------------------------------------------------------------
;Package: BackGammon
Directory("\Program Files\"):-Directory("Games")
Directory("\Program Files\Games"):-Directory("Backgammon")
Directory("\Program Files\Games\Backgammon"):-File("pGammon.exe","\Windows\pGammon.exe")
Directory("\Windows\Start Menu\Games"):-File("Backgammon.lnk","\Windows\Backgammon.lnk")
;END Package: BackGammon
;-------------------------------------------------------------------------------------------
I have two files - f70211a0-0b0a-11de-8c30-0800200c9a66.dsm and f70211a0-0b0a-11de-8c30-0800200c9a66.rgu which are empty. then I have the shortcut and exe file.
I also tried adding REGEDIT4 to the f70211a0-0b0a-11de-8c30-0800200c9a66.rgu file
Am I missing something?
Thanks
DT
Okay removed the rgu file for that app and have successfully built my first ROM - yippee!!!
The only things I noticed and am not sure if it what I have done or a bug, but the phone doesn't switch off. Hold the button and it pops up asking yes or no (as usual) click yes and the phone goes blank. but switching it on again instantly brings you back to the page you were on, it doesn't start from scratch.
Also the Manilla 2D is great, but the email widget doesn't recognise my Exchange email - it wants to create an imap or pop3 account, but says "No Accounts" in the display (even though it shows the unread amount on the icon) - did I do something wrong?
Thanks
D
Sorry double post
Thanks
D
d_train said:
Okay removed the rgu file for that app and have successfully built my first ROM - yippee!!!
Click to expand...
Click to collapse
Congratulations.
The only things I noticed and am not sure if it what I have done or a bug, but the phone doesn't switch off. Hold the button and it pops up asking yes or no (as usual) click yes and the phone goes blank. but switching it on again instantly brings you back to the page you were on, it doesn't start from scratch.
Click to expand...
Click to collapse
Sounds like bug. Which XIP/SYS/OEM combination did you use? Left any packages out? Have a look at others who have built a similar ROM using the combination and check the thread out for bug reports.
thanks will do
The XIP/SYS/ROM I used is - not sure the XIP but I downloaded SYS and ROM version 21109 and used OEM 5.5
How can I extract OEM and SYS from an nbh file?
I have an original ROM installation file that I want to extract some apps for my ROM.
Thanks for your help.
D
I use an old Kaiser kitchen (the first we had, by NetrunnerAT if I remember...) which had tools that can extract automatically NBHs.
But with the newest cooked ROMs, you won't have any "real" OEM or SYS packages since they are protected deleting some files you need to make different folders. You can get the XIP and maybe some individual files but nothing really interesting...
Hi,
I have been using a few kitchens but none of them can dump its own generated ROM back, what I did is:
1. use this kitchen to create RUU_SIGNED.NBH.
2. use this kitchen to dump from NBH file just created.
3. No OEM and SYS directory are created or the directory are created but no files inside.
Can anyone recommend a kitchen which can have files sorted to OEM and SYS in step 3?
Why
HTC_FUZE said:
Hi,
I have been using a few kitchens but none of them can dump its own generated ROM back, what I did is:
1. use this kitchen to create RUU_SIGNED.NBH.
2. use this kitchen to dump from NBH file just created.
3. No OEM and SYS directory are created or the directory are created but no files inside.
Can anyone recommend a kitchen which can have files sorted to OEM and SYS in step 3?
Click to expand...
Click to collapse
Hey HTC_FUZE, Why do you want/need to dump your own ROM? Surely if you have the kitchen - the OEM and SYS are already there! Why don't you just recook with the changes that you want to make to it?
If your trying to dump somebody else's ROM then it may be protected. Some chefs protect their ROMs from being dumped.
Secc
just in case my hdd is dead or files corrupted, so I still have chance to extract rom from my phone and get the same dump as before
Ahhhh...
HTC_FUZE said:
just in case my hdd is dead or files corrupted, so I still have chance to extract rom from my phone and get the same dump as before
Click to expand...
Click to collapse
My best advice to you is to do what i do BACK UP!!! When i first started i never backed my kitchen up, then i lost my whole kitchen, had to start from scratch!! Now, every couple of builds i backup the whole kitchen to a rar and save on a external drive.
A few weeks ago my working kitchen got corrupted somehow, i just restored the rar, imported the new build and was cooking again in no time - without the backup, i'd be knackered!!!
Secc
The OEM folders unfortunately end up in the SYS folder when you dump them. Simply pull them out and put them into the OEM folder and you're set. Something to do with the kitchens recreating the DSM's incorrectly.
@jwzg:
Correct; unfortunately, most kitchens strip the .DSM/.RGU during ROM compilation. Ervius tried to implement a method to preserve the .DSM/.RGU for decompilation but it didn't work as he'd hoped.
@HTC_FUZE:
You need to backup your working kitchen; unfortunately there's no other way. I usually do the following:
File copy the kitchen to a backup HDD
File copy the compiled .NBH I used on the device to a backup HDD
.RAR the kitchen
You could go one extra step and burn the lot to a CD/DVD.
HTH,
This is what I am doing now. However, I would like to have such a kitchen I mentioned. I found one of the ROMs I downloaded can be dumped and sorted like official ROM. I may ask him which kitchen he uses.
I have a Wizard ROM which can be dumped like this. It was made with with an old kitchen that is incompatible with newer devices.
jwzg said:
I have a Wizard ROM which can be dumped like this. It was made with with an old kitchen that is incompatible with newer devices.
Click to expand...
Click to collapse
Hi, Jwzg:
If it is working with Fuze, I would like to have it. Could you give me it? Thanks