Database Users

Custom Dialpad

I've been using the unskinned dialer on my Vogue for the last couple weeks because its much snappier and features an embedded call history. However, after looking at some of the new Diamond custom dialers I've realized I'm not happy with the default skin, so I started pouring over the Windows directory looking for the images that govern the unskinned dialer in hopes I could directly skin it instead of using the dialer overlays.
I was able to find a few files of use, in particular the gifs that control the background color for the call and end keys, the call history images on the left (for call missed/out/in), and the background image. But after changing the files via TotalCommander and soft-resetting, I see no change.
Is there any way to do this without cooking? And does anyone know where else files might be kept for editing this dialer?
ANY help at all would be greatly appreciated.

I'm curious about this too. I've looked all over, but havent been able to find what i'm looking for. Is there a PSD somewhere for the iphone-ish dialers that has the correct splits and things to create our own?

The custom dialers are an alternative to the original dialer...
Look at the files in the CABs for custom dialers, and you will see they have a different set of files. Look at those, and edit them as you want.

Yes, but the custom dialers lose the embedded call history functionality and are sluggish in comparison with wm's default dialer. I don't mind having to cook a rom to get this to work, but I still don't know where all of the images are stored, particularly the ones for the actual number buttons. And perhaps an xml file governing their placement?

Red49er said:
Yes, but the custom dialers lose the embedded call history functionality and are sluggish in comparison with wm's default dialer. I don't mind having to cook a rom to get this to work, but I still don't know where all of the images are stored, particularly the ones for the actual number buttons. And perhaps an xml file governing their placement?
Click to expand...
Click to collapse
Okay...
Maybe this will work...
In the dll files related to the dialer (can't remember there names off hand), there will be graphic files that can be replaced...

Okay, after much searching (now that I knew what I was looking for), I've come up with a list of dlls that may be related:
phcanhtc.dll
phcanoverBMP.dll
dpadmenu.dll
tapres2.dll
tapres.dll.0409.mui
tapres.dll
also, the reg key hklm/security/resover might allow something
Only problem is I realized after continued reading that some of the info I got was related to wm5 roms trying to get smartdialing working like wm6....so if anyone could help me narrow down which dlls are the right ones to edit, that would be fantastic!
also, whats the best way to edit dll and mui files?

Red49er said:
Okay, after much searching (now that I knew what I was looking for), I've come up with a list of dlls that may be related:
phcanhtc.dll
phcanoverBMP.dll
dpadmenu.dll
tapres2.dll
tapres.dll.0409.mui
tapres.dll
also, the reg key hklm/security/resover might allow something
Only problem is I realized after continued reading that some of the info I got was related to wm5 roms trying to get smartdialing working like wm6....so if anyone could help me narrow down which dlls are the right ones to edit, that would be fantastic!
also, whats the best way to edit dll and mui files?
Click to expand...
Click to collapse
phcanhtc.dll -- Contains some BMPs/images
phcanoverBMP.dll -- Contains most of the images
dpadmenu.dll -- Is to do with the dialer workings... Contains no images (I think)
tapres2.dll -- may contain some images
tapres.dll.0409.mui -- is localisation. Mostly just text strings, but may be some images
tapres.dll -- may contain some images
I use "ResHacker" to open up dlls and modify them...

Just tried copying the needed dlls over to my storage card, tried both totalCommander and RescoExplorer, with flight mode off/on, can't get access to tapres.dll, tapres.96.dll, or tapres.dll.0409.mui
Edit: Thanks for the info and the heads up on reshack!

That may be a problem... I'd guess they need to be cooked into the ROM, in which case it may be easiest to take a ROM, dump it, edit the files there, rebuild it and then flash it...

Yeah, I just realized they're rom files and I can't get at them this way.
But I was able to successfully edit phcanoverBMP and change the call history icons.
Thanks for all your help, its cooking time

Red49er said:
Yeah, I just realized they're rom files and I can't get at them this way.
But I was able to successfully edit phcanoverBMP and change the call history icons.
Thanks for all your help, its cooking time
Click to expand...
Click to collapse
No probs!
There are also some files in the WM5 ROM I've dumped in an OEM pack called "Phone_DPI_96" that may be of interest...
they are:
Code:
backarrow_glyph.gif
clg_in.gif
clg_miss.gif
clg_out.gif
cmdpad_land.gif
cmdpad_port.gif
cmdpad_sqre.gif
dialpad_land.gif
dialpad_port.gif
dialpad_sqre.gif
anything beginning with "dlr"
handset_glyph.gif
spd_lst.gif

Okay, so I got ahold of a kitchen, but when I found the tapres dlls in the sys folder, they're not compiled -- its a bin file, 2 txts, and an s000. Reshack can't do anything with these files. What do I do?

You need to use "Reversemode" to turn those into a dll, then you can edit that.

I googled reversemode, and all I came up with was reversemode.com which didn't look like any sort of software that would help with this.

Red49er said:
I googled reversemode, and all I came up with was reversemode.com which didn't look like any sort of software that would help with this.
Click to expand...
Click to collapse
I'll be more helpful then
This post: http://forum.xda-developers.com/showthread.php?t=331094

well this seems to be a brick wall. no matter which file I try to use revresmode on, it says it doesn't work on .net files.
Thanks for the help anyways tho.

I don't know about changing the font of the dialer, but you can change the dialer within the rom contents (only the buttons and background) I found that there are two separate folders in the SYS folder. the files are read only. unlock them and edit in photoshop. you don't have to relock them to cook them back in, just save them in the same exact format they were in before you unchecked the "readonly". That is how I edited mine. I have no idea why why anyone would bother trying to mess with the dll's?!!!

S.V.I said:
I don't know about changing the font of the dialer, but you can change the dialer within the rom contents (only the buttons and background) I found that there are two separate folders in the SYS folder. the files are read only. unlock them and edit in photoshop. you don't have to relock them to cook them back in, just save them in the same exact format they were in before you unchecked the "readonly". That is how I edited mine. I have no idea why why anyone would bother trying to mess with the dll's?!!!
Click to expand...
Click to collapse
There are embedded images in the DLLs...
You need to use reversmode on the folder, not the files within it...

l3v5y said:
You need to use reversmode on the folder, not the files within it...
Click to expand...
Click to collapse
Doing that gives me a "cannot open input file" error. And yes, all files and folders are not marked as read only.

Red49er said:
Doing that gives me a "cannot open input file" error. And yes, all files and folders are not marked as read only.
Click to expand...
Click to collapse
My mistake! Reversmod does dll to module, RecMod (attached) does the reverse...
Sorry!

Cooking SDKCERT in ROM

Hallo everybody,
I just want to ask how I can built in SDKCERT directly into ROM.If I want to convert SDKCERT.CAB to EXT then after I have again CAB so newerending story.

You won't need to use the SDKCERT package. If you are using Ervius Visual Kitchen for example, all you need to do is ensure that Disable Cert(ificate) checking is selected. This way, your compiled ROM will already have Certificate checking disabled allowing you to install updated drivers and such.
This tutorial discusses some of the changes you'll likely need to make:
http://forum.xda-developers.com/showthread.php?t=526610
HTH,

if you still need it ,here its is. just add to any package.

faria said:
if you still need it ,here its is. just add to any package.
Click to expand...
Click to collapse
Thank you very much!!!

Johan Kraczmar said:
Thank you very much!!!
Click to expand...
Click to collapse
Np.
Here is a little tip for future...
most certificates are in cab form,open the cab with winrar,you will see a file called;_setup.xml, that is the cert info.
just rename _setup.xml to mxip_999_certname.provxml and you done.

faria said:
if you still need it ,here its is. just add to any package.
Click to expand...
Click to collapse
Did I understand correctly that I would need to add this to each package that needs a certificate?
Thanks

He said that you need to add this in every cab that need certificates, if you use EVK or Oskitchen you dont need anything because they auto patch the certs.
Lewy1 said:
Did I understand correctly that I would need to add this to each package that needs a certificate?
Thanks
Click to expand...
Click to collapse

af974 said:
He said that you need to add this in every cab that need certificates, if you use EVK or Oskitchen you dont need anything because they auto patch the certs.
Click to expand...
Click to collapse
Thanks. The problem is that I've tried quite a few times to install the Vogue Camera as an EXT with EVK, and I always end up with the "The file 'camera' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found." etc.

Did you tried the solution in post #3?
For which device are you trying to install?...from Vogue to -> ?
Sometimes from different devices isnt a certificate fault but some missing dll.
Check for this app Dependency walker and search if you have all the modules to make run camera Vogue.
Lewy1 said:
Thanks. The problem is that I've tried quite a few times to install the Vogue Camera as an EXT with EVK, and I always end up with the "The file 'camera' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found." etc.
Click to expand...
Click to collapse

Lewy1 said:
Thanks. The problem is that I've tried quite a few times to install the Vogue Camera as an EXT with EVK, and I always end up with the "The file 'camera' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found." etc.
Click to expand...
Click to collapse
Hi Lewy1,
You are missing a package dependency. If you navigate to the .\Windows folder using File Explorer on your device and try and launch the Camera application, you will encounter an error - confirming that you have dependency issue.
Have a look at this post:
http://forum.xda-developers.com/showpost.php?p=4259031&postcount=1070
HTH,

Lewy1 said:
Thanks. The problem is that I've tried quite a few times to install the Vogue Camera as an EXT with EVK, and I always end up with the "The file 'camera' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found." etc.
Click to expand...
Click to collapse
Yeah, that is just a generic error message, and it almost never has anything to do with certs. You could be missing dependencies, or it could just be that you have a broken shortcut. One of the problems with the 6.5 start menu is that you can't always tell just by looking that the shortcut is effed, because you may have an ico assigned through the registry. Use Total Commander to see if you have the correct shortcut path.

hilaireg said:
Hi Lewy1,
You are missing a package dependency. If you navigate to the .\Windows folder using File Explorer on your device and try and launch the Camera application, you will encounter an error - confirming that you have dependency issue.
Have a look at this post:
http://forum.xda-developers.com/showpost.php?p=4259031&postcount=1070
HTH,
Click to expand...
Click to collapse
Farmer Ted said:
Yeah, that is just a generic error message, and it almost never has anything to do with certs. You could be missing dependencies, or it could just be that you have a broken shortcut. One of the problems with the 6.5 start menu is that you can't always tell just by looking that the shortcut is effed, because you may have an ico assigned through the registry. Use Total Commander to see if you have the correct shortcut path.
Click to expand...
Click to collapse
First of all, thanks guys for your help!
Yes, your right that the problem is also when I try launching the camera from the windows directory. Now the problem is that I don't understand too much when it comes to digging into the contents of these files, so I think I'll need some help.
I assumed I needed Dependency Walker which you wrote about in your Kitchen Utensils review, so I opened the camera.exe and the results are attached as a Dependency Walker Image. The camera EXT I have come from converting a cab that's been floating around XDA. By the way I had the same problem when using the mega camera.
Thanks so much for the patience and help.

Had a look at the .DWI file you attached. Your next steps:
Create a folder on your system (ex: C:\WINMO_OS)
Copy all of the camera package files to the folder.
In DEPENDS, remove all of the "Module Search Order" paths - Options menu.
Add the folder path (ex: C:\WINMO_OS)
Search your kitchen for each file that is listed in CAMERA.EXE and copy them to the folder.
Once you have the files from CAMERA.EXE in the folder, open each of the yellow ( ? ) files.
Repeat the steps above until you have examined all of the files in the folder you created.
Essentially, you want to locate all of the files listed in each .DLL, .EXE, etc. that is displayed in DEPENDS.
If the files appear in the .\SYS or .\OEM folder, it's likely those aren't the issue. Some files may be modules; it's likely those aren't the issue as well - I usually RECMOD a copy of the file and place it in the folder or I copy it from the device when connected using USB. This will reveal additional files that are "missing". I suspect you will discover the missing dependency to be in another file. If you find the files in packages, it's likely the entire package is a dependency. If you can't find a file, make note of it and continue on. At the end, post the list of files you couldn't find.
Lastly, examine each of the .REG files for references to other files; you may need to do a global search through the kitchen to find other packages that may be writing to the same keys ... these will likely be dependant packages as well.
HTH,
* EDIT *
If at all possible, it would be beneficial for you to find the official source ROM that the package originated from.

hilaireg said:
Had a look at the .DWI file you attached. Your next steps:
Create a folder on your system (ex: C:\WINMO_OS)
Copy all of the camera package files to the folder.
In DEPENDS, remove all of the "Module Search Order" paths - Options menu.
Add the folder path (ex: C:\WINMO_OS)
Search your kitchen for each file that is listed in CAMERA.EXE and copy them to the folder.
Once you have the files from CAMERA.EXE in the folder, open each of the yellow ( ? ) files.
Repeat the steps above until you have examined all of the files in the folder you created.
Essentially, you want to locate all of the files listed in each .DLL, .EXE, etc. that is displayed in DEPENDS.
If the files appear in the .\SYS or .\OEM folder, it's likely those aren't the issue. Some files may be modules; it's likely those aren't the issue as well - I usually RECMOD a copy of the file and place it in the folder or I copy it from the device when connected using USB. This will reveal additional files that are "missing". I suspect you will discover the missing dependency to be in another file. If you find the files in packages, it's likely the entire package is a dependency. If you can't find a file, make note of it and continue on. At the end, post the list of files you couldn't find.
Lastly, examine each of the .REG files for references to other files; you may need to do a global search through the kitchen to find other packages that may be writing to the same keys ... these will likely be dependant packages as well.
HTH,
* EDIT *
If at all possible, it would be beneficial for you to find the official source ROM that the package originated from.
Click to expand...
Click to collapse
Thanks, that was quick. Looks like I got a lot of work ahead of me.

[Resolved] Tcpmp issue

Guys, Can't seem to get TCPMP to work in my Custom ROM. I know there are some Regs that are not being applied when cooking as the ROMs accept only Cab installed TCPMP to play. Can someone please share their working TCPMP or tell me how to tweak it to work when cooked. I know NRGZ has one working in his ROM and others out there so, plz share before we start thinking of other xtreme ways....LOL!

Try the one in post 1.
http://forum.xda-developers.com/showthread.php?t=670465
One issue with tcpmp is that is uses a dll named common.dll. The package I use puts tcpmp in windows-the dll goes there, too. Make sure it isn't over-written by a dll of the same name from another package. OMarket also uses a common.dll, so if you cook both into windows, only one will work.

Farmer Ted said:
Try the one in post 1.
http://forum.xda-developers.com/showthread.php?t=670465
One issue with tcpmp is that is uses a dll named common.dll. The package I use puts tcpmp in windows-the dll goes there, too. Make sure it isn't over-written by a dll of the same name from another package. OMarket also uses a common.dll, so if you cokk both into windows, only one will work.
Click to expand...
Click to collapse
Thanks Man, Appreciate. Downloading now will report after cooking at home tonite

Farmer Ted said:
Try the one in post 1.
http://forum.xda-developers.com/showthread.php?t=670465
One issue with tcpmp is that is uses a dll named common.dll. The package I use puts tcpmp in windows-the dll goes there, too. Make sure it isn't over-written by a dll of the same name from another package. OMarket also uses a common.dll, so if you cokk both into windows, only one will work.
Click to expand...
Click to collapse
Tough going mate. Its crushing my platformrebuilder...

Look at your build-log, and make sure you don't already have any of the modules in the package (common.dll, WMADMOD.DLL, WMSDMOD.DLL, WMVDMOD.DLL). I have a feeling you're already cooking in a common.dll, and that's why the package you were using before wouldn't work; over-writing it with another module could cause prb to crash.
Edit: Also, make sure there aren't any registry parsing errors. I've gotten them for the DLL Path key before, although EVK normally just ignores the problem. I might have dumped those keys with total commander, and it doesn't get the path right (either too many or not enough '\'s). You can just delete those keys, if they're causing issues.
You really don't even need the reg file; tcpmp just loads a default set of keys if HKLM\TCPMP is empty. The only key you really want is the one for the skin file (\windows\skin.xml).
You can also try out the Uzard package posted a little later in the thread. It has a combo of Uzard browser/TCPMP. If you don't want the browser, just dump it. The tcpmp reg keys should be fine in that one.

Farmer Ted said:
Look at your build-log, and make sure you don't already have any of the modules in the package (common.dll, WMADMOD.DLL, WMSDMOD.DLL, WMVDMOD.DLL). I have a feeling you're already cooking in a common.dll, and that's why the package you were using before wouldn't work; over-writing it with another module could cause prb to crash.
Edit: Also, make sure there aren't any registry parsing errors. I've gotten them for the DLL Path key before, although EVK normally just ignores the problem. I might have dumped those keys with total commander, and it doesn't get the path right (either too many or not enough '\'s). You can just delete those keys, if they're causing issues.
You really don't even need the reg file; tcpmp just loads a default set of keys if HKLM\TCPMP is empty. The only key you really want is the one for the skin file (\windows\skin.xml).
You can also try out the Uzard package posted a little later in the thread. It has a combo of Uzard browser/TCPMP. If you don't want the browser, just dump it. The tcpmp reg keys should be fine in that one.
Click to expand...
Click to collapse
Thanks, will try again after I get it to go past first boot screen. The Packages have messed up my Kitchen, I am trying to reset it again.

Farmer Ted said:
Look at your build-log, and make sure you don't already have any of the modules in the package (common.dll, WMADMOD.DLL, WMSDMOD.DLL, WMVDMOD.DLL). I have a feeling you're already cooking in a common.dll, and that's why the package you were using before wouldn't work; over-writing it with another module could cause prb to crash.
Edit: Also, make sure there aren't any registry parsing errors. I've gotten them for the DLL Path key before, although EVK normally just ignores the problem. I might have dumped those keys with total commander, and it doesn't get the path right (either too many or not enough '\'s). You can just delete those keys, if they're causing issues.
You really don't even need the reg file; tcpmp just loads a default set of keys if HKLM\TCPMP is empty. The only key you really want is the one for the skin file (\windows\skin.xml).
You can also try out the Uzard package posted a little later in the thread. It has a combo of Uzard browser/TCPMP. If you don't want the browser, just dump it. The tcpmp reg keys should be fine in that one.
Click to expand...
Click to collapse
Thanks, will try again after I get it to go past first boot screen. The Packages have messed up my Kitchen, I am trying to reset it again.
even after removing them Rom won't boot up after customisations. Wierd

Hi,
the attached TCPMP Package works fine for me.
with friendly greet
starbase64

starbase64 said:
Hi,
the attached TCPMP Package works fine for me.
with friendly greet
starbase64
Click to expand...
Click to collapse
Thanks Mate. I am cooking it in right now.
Edit: Just cooked it in and I confirm that its working, even with OMarket's Common.dll in the Rom. Thanks a million starbase64 >>>Issue now closed.

So common.dll was the problem? I knew it, lol.
You could save rom space by cooking tcpmp straight into rom and putting OMarket into \Program Files either with a cab or a zip install. The other way to do it is with an app.dat file, but you need to name common.dll (for OMarket) something like 000-common.dll in rom and have it renamed to common.dll when it is copied to the new location by initflashfiles.dat. That way, you won't have two different files named common.dll in conflict w/ each other during cooking, with one over-writing the other.

Farmer Ted said:
So common.dll was the problem? I knew it, lol.
You could save rom space by cooking tcpmp straight into rom and putting OMarket into \Program Files either with a cab or a zip install. The other way to do it is with an app.dat file, but you need to name common.dll (for OMarket) something like 000-common.dll in rom and have it renamed to common.dll when it is copied to the new location by initflashfiles.dat. That way, you won't have two different files named common.dll in conflict w/ each other during cooking, with one over-writing the other.
Click to expand...
Click to collapse
noted.thanks for all the help man!
peace.

Well, I remember the first time I cooked omarket in, and I was left wondering why the hell tcpmp no longer worked. I wish that developers wouldn't name there modules and files with such bland names. I'm pretty much maxed out on files named settings.txt, settings.cfg, settings.ini, settings.config and settings.xml right now in my windows folder. One more, and I'll be screwed. Oh, wait, I've got a settings.db in there, too, lol.

[Q] OEM package with dll

hey there,
i created an oem package which contains an dll file, one that exists also in the sys-folder as folder (contains imageinfo.bin and s000), when cooking with my kitchen buildos gives an error, something about that the expected file already exists as folder...
what can i do?

It's not a good idea to over-write a module; in fact, it's a bad idea, because it crashes most kitchens (buildos will crash every time).
1. Why are you trying to over-write a module with a file?
2. If you really want to do it, you need to remove the module from the sys directory. I'm not sure it's a good idea myself; you should at least convert the file to a module. If you don't know the difference between a file and a module, then you should search and find the answer. It's easy enough to do.
It would help a great deal when you start a topic if you give more information. What build are you using? What device? Most importantly, what module are you trying to replace?

Thanks Ted,
sorry for the small amount if informations. I'm using EXEcutor von pako777, it's kitchen tool for the omnia 2... almost, it dissambles the dump-file, then i can delete/add files and then it assembles it again... some kitchens i saw over here a really great, but the executor get the work done...
i found the informations, thanks for the hint i will now try reversmode.exe
right now i want to convert a taskbar.cab to an oem package and so i need to replace shellres.192.dll and some other files

I think that kheb 1.1 (search, it's easy to find) is the best way to make a package for your cab. Just run a snapshot, install the cab, then run another snapshot (+difference). Select the 'make an oem' function. It doesn't make a working oem, but it will dump the reg keys that you need, and collect all the files (I assume they'll all go to windows). It sounds like you're building the rom straight from a dump, and not with full packages? Then you'll need to just swap the new files in for any old ones (as well as add new ones), and figure out how to add the registry keys, if there are any. I guess you can use ceregeditor or something similar to import the keys into the default.hv. Convert files to modules, if that's how the dll's appear in the dump.
You have to be a little careful with an app like kheb (or sk tracker): it may dump out some extraneous files or reg keys, as changes occur all the time to a device's registry and file system. Make sure you separate the wheat from the chaff. It's best not to soft reset after the cab install, if you're prompted to do so. That creates a butt-load of random new reg values that are irrelevant. If any certificates are installed by the cab, you can probably ignore them.

Thanks again, but i used the package creator from ervius to convert the cab, converted the rgu to an provxml and the dll-files with reversmode and everything worked fine
but i will take a look onto kheb, sound promising when converting a cab with setup.dll

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.