Develop Bugs

[Q]Replace/update OEM packages and other issues...

First of all I'm sorry for my english, hope you can understand me...
I'm going to cook my first ROM...
The idea is to make 2 versions (with/without manila) of a clean "uc capable" rom; what I want to do is take a 1.93 official base and update some oem app and sys (i.e. htc camera and netcf) and remove some others to replace theese with 3t part usefully app (i.e. putting in wktask manager instead htc task).
Now my doubts:
(I've readed a lot of wikies and thread but didn't find a CLEAR answer to all my questions)
1- If I use an official .exe rom as base I obiouvsly find inside it the radio part...have to remove this befor but in base folder due i don't need it for my work? How?
2- I'm able to remove oem pack from my rom base and I'm also able to repack new ones starting from a cab file...but I don't know if it's possible to take (exactly as they are) some oem pack from a stock/custom(when not protected) rom to use in mine...I saw that a lot of cookers use oem pack taken from raphael official roms to update thair roms and I would know if the process to do this is just open the rom, copy the oem and past it in mine... In this case...where can I find a good very update raphael rom?!
3- Opposite than this, for manila I would use the "animated switches" version. I want to downgrade it to the version with theese animations but I don't know if there's a particular process to replace this oem...can you tell me? PS: what is the exact manila version I need to do it?
4- TO UPDATE NETCF TO THE 3.5 VERSION WHAT HAVE I EXACTLY DO? And is the Alexandre's oem pack good for my pourpose?
Thank you a lot and sorry if (maybe) some questions were answered in other threads...I searched and readed a lot but there are too many informations in this forum for a noob/bad english speaker/... like me so I decided to ask!

GriFolle said:
First of all I'm sorry for my english, hope you can understand me...
I'm going to cook my first ROM...
The idea is to make 2 versions (with/without manila) of a clean "uc capable" rom; what I want to do is take a 1.93 official base and update some oem app and sys (i.e. htc camera and netcf) and remove some others to replace theese with 3t part usefully app (i.e. putting in wktask manager instead htc task).
Now my doubts:
(I've readed a lot of wikies and thread but didn't find a CLEAR answer to all my questions)
1- If I use an official .exe rom as base I obiouvsly find inside it the radio part...have to remove this befor but in base folder due i don't need it for my work? How?
2- I'm able to remove oem pack from my rom base and I'm also able to repack new ones starting from a cab file...but I don't know if it's possible to take (exactly as they are) some oem pack from a stock/custom(when not protected) rom to use in mine...I saw that a lot of cookers use oem pack taken from raphael official roms to update thair roms and I would know if the process to do this is just open the rom, copy the oem and past it in mine... In this case...where can I find a good very update raphael rom?!
3- Opposite than this, for manila I would use the "animated switches" version. I want to downgrade it to the version with theese animations but I don't know if there's a particular process to replace this oem...can you tell me? PS: what is the exact manila version I need to do it?
4- TO UPDATE NETCF TO THE 3.5 VERSION WHAT HAVE I EXACTLY DO? And is the Alexandre's oem pack good for my pourpose?
Thank you a lot and sorry if (maybe) some questions were answered in other threads...I searched and readed a lot but there are too many informations in this forum for a noob/bad english speaker/... like me so I decided to ask!
Click to expand...
Click to collapse
1. When dumping a ROM, it will dump separately the splashes, radio, os and extrom (if any.) Extract the exe with WinRAR and dump the nbh.
2. When dumping a ROM, it will create packages if ROM is unprotected. A good place of finding a Raph ROM would be the Raphael forums.
3. Delete the old package from kitchen and replace with new one (in your case, the old one, animated).
4. You can find ready made NetCF 3.5 packages. You should delete the old NetCF 2 from SYS folder and replace it with the 3.5

tnyynt said:
1. When dumping a ROM, it will dump separately the splashes, radio, os and extrom (if any.) Extract the exe with WinRAR and dump the nbh.
2. When dumping a ROM, it will create packages if ROM is unprotected. A good place of finding a Raph ROM would be the Raphael forums.
3. Delete the old package from kitchen and replace with new one (in your case, the old one, animated).
4. You can find ready made NetCF 3.5 packages. You should delete the old NetCF 2 from SYS folder and replace it with the 3.5
Click to expand...
Click to collapse
Thanks a lot!
So, to replace OEM, just put out (from a rom) and put in (in mine)...so simple?!
Ahahah...

Please, excuse me for my stupidity...BUT I REALLY NEED AN HELP!!!
(I'm following this guide: http://forum.xda-developers.com/showthread.php?t=413782&highlight=kitchen)
Here's what I do:
1) I've downloaded from htc site the last official stock rom (localized for my country) \HTC Touch Diamond\QMR\RUU_Diamond_HTC_ITA_1.93.408.3_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship
2) I've extracted all files and putted them into Base ROM folder of surface kitchen.
3) clicked on begin and obtained some folders in the kitchwen one
Now if I go into one package folders in OEM (htc gesture in example) i can't see dsm or rgu files, but just dll and .provxml ones...WHY?! I don't think it's good, right? Where is my fault?!
SO SAD...
PS: I've searched a lot but I've not found a netcf prepared package to cook...
Thanks a lot!

GriFolle said:
Please, excuse me for my stupidity...BUT I REALLY NEED AN HELP!!!
(I'm following this guide: http://forum.xda-developers.com/showthread.php?t=413782&highlight=kitchen)
Here's what I do:
1) I've downloaded from htc site the last official stock rom (localized for my country) \HTC Touch Diamond\QMR\RUU_Diamond_HTC_ITA_1.93.408.3_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship
2) I've extracted all files and putted them into Base ROM folder of surface kitchen.
3) clicked on begin and obtained some folders in the kitchwen one
Now if I go into one package folders in OEM (htc gesture in example) i can't see dsm or rgu files, but just dll and .provxml ones...WHY?! I don't think it's good, right? Where is my fault?!
SO SAD...
PS: I've searched a lot but I've not found a netcf prepared package to cook...
Thanks a lot!
Click to expand...
Click to collapse
You have to create the packages!
Don't know the kitchen but it should be like this in every kitchen.
Also, you can check inside provxml file (notepad will do), maybe the rgu (registry entries) are set through provisioning.

tnyynt said:
You have to create the packages!
Don't know the kitchen but it should be like this in every kitchen.
Also, you can check inside provxml file (notepad will do), maybe the rgu (registry entries) are set through provisioning.
Click to expand...
Click to collapse
confused...
I think I have to create just the packages of apps I would to add...not even all the apps contained in the stock rom!
Looking and reading tutorials in this forum I understood that If I would (i.e.) add/rmv apps to my rom I've just to put its files in base rom and then (after extract all) add/remove what I want. Then rebuild.
But for all others teorically I don't do anything...Is this wrong?
PS: thank you for the previous reply

Port XIP

Hello every1
I've tried to port 20755 xip from xip.bin (20755). I think I've done every thing allright. Because I can read OS CE 5.2.20755 in About. But, with this new XIP I can not send or transfer files. I can't select this option with File Explorer.
I've came back to my last ROM folder (20273) and It works properly.
I use Bepe's extended kitchen. there are \XIP folder, OS.nb.payload, out.bin (I think it's XIP) and another file, *.bin (I don't remember now), into \ROM folder.
What am I doing bad ?
Thanks in advance.
Best regards !!!

Did you port any of the modules or files that belong to the OEM packages? This can cause all sorts of issues.

mpattman said:
Did you port any of the modules or files that belong to the OEM packages? This can cause all sorts of issues.
Click to expand...
Click to collapse
Thanks.
Yes, I've ported everything. I'll try again without porting that folder.
Regards !
EDIT: Everything has gone properly. THX.

[Q] Help porting SYS to new rom.

Need help porting sys folder..
I've successfully ported XIP to 20757 and now i've been trying to port the sys build folder 20757 and up, from multiple roms, such as the xperia x1 roms, the blackstone roms, and other's from the site.
But all of my attempts has fail, so was hoping someone could tell me what im doing wrong.
First sys attempt i tried was;
How to port a SYS folder
Open your old SYS folder and copy the .VM and WinCENLS_WWE folders into your new SYS folder
Go to your old SYS\Shell and copy shell32.exe and shellres.dll into your new SYS\Shell
found here http://forum.xda-developers.com/showthread.php?t=389772
Second i tired, to port it from a thread on the kaiser forum, http://forum.xda-developers.com/showthread.php?t=437264
and third i tried this following guide from the elf forms, http://forum.xda-developers.com/showthread.php?t=379598
so for short
1. made 1 folder for old sys, and 1 for new system with the build number
2. copy .vm .rom WinCENLS_WWE, shell/shellresand shell/shell32 folder, with my already ported XIP
3. swap out the res folder like 800 and 640 ones for the diamond, (where ever it is needed to port the rom)
4. then ran g'reloc
so yeah finally when i tried all this, form the guide, it doesnt work

What about the easiest way?
Take a look here:
http://forum.xda-developers.com/showthread.php?t=452779

Ervius's tool is to port XIP
To port SYS is the easiest porting Simply run Greloc on old SYS and note all the values. Then run Greloc on new SYS and change the values as per old SYS. No replacement needed, no swapping required
Simple!

ababrekar said:
Ervius's tool is to port XIP
To port SYS is the easiest porting Simply run Greloc on old SYS and note all the values. Then run Greloc on new SYS and change the values as per old SYS. No replacement needed, no swapping required
Simple!
Click to expand...
Click to collapse
I thought that to but every time i tried to port the Blacstone sys and Greloc
the rom doesnt boot, I have tried many times and allways the same result.
havent test for a wile, the xip port I get whit your exellent manual xip port but not the sys, so now I have a rom os 20757 Build 19665

have you tried replacing all except the Metadata folder ?
for your XIP which is the base used 1.93, 1.96, 1.97 ?
I have tried the xiportereex tool but some modules are missing, so I tryied to add it by myself, it boot but sometime touch screen doesn't responde at first tap, very strange, I have also a pb with default ringtone witch is not the one it should be by mxipupdate

hi
thank you for your reply everyone but several attempts trying you methods but none has worked ; ;
UPDATE; i give up trying to port sys build, thnx for you help everyone.

Same problem for me, if I try all these method in order to port the sys 20764 ( blackstone) to me ELF, the phone don't boot :-(

if the problem is running poutlook, please check if you have custsat.dll in your rom.
if removed, poutlook won't run.

This is the sam exact problem i'm running into. I can't just not port the SYS because the XIP i'm using opens the windows in a tiny little corner in the top left hand corner. Has anyone figured out how to actually port the SYS since none of the tutorials seem to work.

Hi All,
Try this:
1. Copy all modules and dsm ONLY from these few folders (BaseApps, Shell, Phone, PhoneRedist and Redist) from new SYS to your old SYS folder. No need copy ***_DPI_*** (images), ***_0409 / ***_0804 (language files) and the rgu because they never change even how high the build number goes
2. Copy gwes.exe from new build OS folder to your OS folder (if you don't want to get small little window on the top left corner)
3. g'reloc
4. Cook
Good luck !

Bxsteez said:
a tiny little corner in the top left hand corner
Click to expand...
Click to collapse
take gwes.exe from a vga rom and replace that... you have same problem I had the sys was from a no vga rom and when I took the gwes from my stock rom it make the trick gwes.exe u find in Os folder

Vic5870 said:
Hi All,
Try this:
1. Copy all modules and dsm ONLY from these few folders (BaseApps, Shell, Phone, PhoneRedist and Redist) from new SYS to your old SYS folder. No need copy ***_DPI_*** (images), ***_0409 / ***_0804 (language files) and the rgu because they never change even how high the build number goes
2. Copy gwes.exe from new build OS folder to your OS folder (if you don't want to get small little window on the top left corner)
3. g'reloc
4. Cook
Good luck !
Click to expand...
Click to collapse
In fact, you can take the rest of the OS folder too, with the exception of the rgu and ossvcs

omaga said:
take gwes.exe from a vga rom and replace that... you have same problem I had the sys was from a no vga rom and when I took the gwes from my stock rom it make the trick gwes.exe u find in Os folder
Click to expand...
Click to collapse
I had this problem when i was porting the Touch HD ROM to the Xperia X1 and thats wvga to wvga. I honestly thought porting the SYS would be the easy part but the SYS is why my phone doesn't boot up it just sits there

Bxsteez said:
I honestly thought porting the SYS would be the easy part but the SYS is why my phone doesn't boot up it just sits there
Click to expand...
Click to collapse
Ye I thought that sys is the easy part I got so many sys port that the rom doesnt boot. Now i get 2 in a row 21109 and 21014 sudden and If I remember right I have allways done the same way

Thats the one that i'm working on now. I'm trying to port the 21109 from the touch pro to the xperia but i can't get it to work. Can u give me any tips?

Bxsteez said:
Thats the one that i'm working on now. I'm trying to port the 21109 from the touch pro to the xperia but i can't get it to work. Can u give me any tips?
Click to expand...
Click to collapse
Maybe you should post in the X-Peria ROM dev. forum!?

I have but as we all know the xperia doesn't get as much attention as to the full blown htc devices. I figure that the porting method should be about the same with the exception of changing some things based on resolution. Am i wrong?

Have you deleted some folders from official HD SYS??
If yes, notice that the rom doesn't boot without SqlCeMobile and SqlCeMobile_Lang_0409 folders. I'm speaking from my experience with HD.
And I remember I've ported these official builds to Toshiba G900 without problems. Then, make attention to these things too.
And control if into your original SYS, you have some different folders in comparison to the new SYS.
Another thing, Ervius xipporterex rev-35, deletes some things from xip, but it works perfect in that way. The only thing you have to notice, is that it deletes WinCENLS_WWE from xip, then you have to add it into SYS folder.
@Bxsteez,
chek your 21109 SYS, and change mxip_system.vol(into Shell), with your original and see if mxipcold_wpc_2.provxml is into Base_DPI_192 folder, if not, copy your original one there. Change MobileCalculator.exe into baseapps folder too.

Just gave this a shot and nothing works again.... I can't even port the XIP and use the standard SYS and get it to boot. I wonder if i'm using a some corrupted build of 21109. Can someone point me in the direction of where to get OS CE 21109 and 21109 build?

Search on ppcgeeks the calkulins kitchen for diamond, then extract the xip from os.nb.payload and use that to port, worked for me with ervius xipporterex-35.
And make those changes into SYS folder, they are needed to boot properly.

6.5 21159 hangs on welcome screen.

Can anyone give me some insight on this problem. I am porting 21159 to the Treo 700wx, and it keeps stopping on the WM 6.5 startup screen. I can turn off/on the display, but it never progress onto screen calibration or anything else.
I have replaced the gwes.exe file in order to get the rom to boot, as well as wincenls_wwe, but it doesn't seem to make any difference. At the moment, I'm stumped. Any help would be greatly appreciated.
86 views so far, and no replies. That can't be good...

I think I might need a gwes.exe for 240x240 screen on a 211xx build. Does anyone have one?

Any progress?

untarded said:
Any progress?
Click to expand...
Click to collapse
Nope. No responses. I did find a 6.5 rom for the treo 750, but they removed all of the dsm files, so I can't port it. I have to try to manual piece it back together.

This is really a good build, but believe me that stabilniejszy is 21,109, this is fast

stuck at boot screen usually because of
1. wrong xip porting
2. wrong wince_nls
that is what i am facing now also

cruzzmz said:
stuck at boot screen usually because of
1. wrong xip porting
2. wrong wince_nls
that is what i am facing now also
Click to expand...
Click to collapse
not necessarily. i had the same troubles too and i got it working after including HTC's TouchFLO OEM package and ConfettiCore package (which i was deleting before) in SYS.

!Aman! said:
not necessarily. i had the same troubles too and i got it working after including HTC's TouchFLO OEM package and ConfettiCore package (which i was deleting before) in SYS.
Click to expand...
Click to collapse
both of the above is not in the rom? could you share the link of ur successful SYS folder somewhere

cruzzmz said:
both of the above is not in the rom? could you share the link of ur successful SYS folder somewhere
Click to expand...
Click to collapse
i think all of the SYS 21159 floating around have ConfettiCore package inside, so u can try any. i thought it was useless, so deleted it. but it lead to the problem mentioned above. in addition to that, i had to use TOuchFLO OEM package also of my device which i deleted coz i wanted to use M$ default touchflo.

!Aman! said:
i think all of the SYS 21159 floating around have ConfettiCore package inside, so u can try any. i thought it was useless, so deleted it. but it lead to the problem mentioned above. in addition to that, i had to use TOuchFLO OEM package also of my device which i deleted coz i wanted to use M$ default touchflo.
Click to expand...
Click to collapse
sad to say dude of of the rom now have protection on it including urs so i cant use package tool to make it to SYS folder ....

cruzzmz said:
stuck at boot screen usually because of
1. wrong xip porting
2. wrong wince_nls
that is what i am facing now also
Click to expand...
Click to collapse
Already tried this. Both are correct. It's not hangs on the boot screen. It's hanging on the welcome screen. Well it's not exactly hanging. I can still power it on and off. I still get the press the middle button to unlock thing. I can turn the radio on and off. It just never moves on from the welcome screen.

I pieced some of the 750 rom into my SYS. I noticed they had modified some of the .cpr files for 240x240, so I included those as well. Flashing now, we'll see what happens.
Update: Same problem. It stops at the welcome screen.

Tryed using my existing .rom folder, and shell32.dll and shellres.dll. Still no luck.

same problem since 21xxx builds with welcome-center
I'am a german rom-cooker for glofiish m800-device.
i work since over one week on windows mobile 6.5.
I'am not success today.
The Problem is:
- No Calibration (Welcome.lnk) is launched by initflashfiles.dat
but in the file the entry is included
the biggest problem, becouse the device is unusable
- The Startmenu is wrong, only a white screen open. (very small) no solution with gwes.exe from wm61 20924 sys.
- the grey taskbar on the today-screen
i have replaced gwes.exe from working windows mobile 6.1 sys 20924
i have changed shell.exe and shellres32.dll in shell-directory from sys
to change user.hv and default.hv from metadata
to delete user.hv and default.hv from metadata
to replace folder for shell
to replace folder for phone
to replace folder for redist.
to include wince.nls in sys-folder too
The wince.nls is in my xip (rom-directory) (my kitchen need the extracted version of xip.bin)
I don't know what the problem is.
I have ported XIP 21159 from Diamond, from TouchPro, from glofiish m700, from glofiish m500 and much more. I'am sure i use actually an VGA-XIP (from Diamond, 1.post in this Thread)
but i don't know which version this is (21139 or 21159 ???)
all the same problem.
i use my kitchen based on windows mobile 6.1 and included the g'reloc.exe from WM65 Kitchen (forwarder) and the wmreloc.exe.
since my kitchen is ready for wm65. all works great by compiling the new temp.dat (the flash-file for glofiish devices)
I read i must use the same sources for XIP and SYS !!!
But what are the same Sources ???
Can anyone send me an working 21159 XIP for VGA ???
When i try to port "Diamond Payload 21159" from XDA-Developers with Xipport and Xipporterex the xip is ok, but when i insert in my kitchen, the prog "buildos" stop their working, nothing happens in command-window.
So i'am very pleasent when you can send me an working source 21159 SYS for VGA and an working Source 21159 XIP for VGA...
i have big problem with windows mobile 6.5
acutally i try windows mobile 6.1 21114 there are the same problem.
the problem is, after os-logo no calibration screen come.
big problems to call "welcome.lnk"
only whenn i insert in wrong path to welcome.lnk the today-screen display ???
do you know this bug ???
here is the rgu of the welcome-center, i think it's not compatible with m800 ???
is this welcome-center new in the 21xxx-builds ???
over one week and no succed with wm65.
at the moment the same problems with wm61 21115
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Rai\:M SWelcomeCenter]
"0"="MSWelcomeCenter" ; class name
"1"="wcsan.exe" ; exe to launch
"2"=dword:1 ; perf hint (RAI_PERF_*)
"3"=dword:0 ; app type (?)
[HKEY_LOCAL_MACHINE\Software\Microsoft\CHome\CWelco meCenter]
"Disabled"=dword:0
[HKEY_CLASSES_ROOT\.wcml]
@="wcmlfile"
"Content Type"="text/html"
[HKEY_CLASSES_ROOT\wcmlfile\DefaultIcon]
@="browsres.dll,-6703"
[HKEY_CLASSES_ROOT\wcmlfile\Shell\Open\Command]
@="iexplore.exe file:%1"
[HKEY_CLASSES_ROOT\welcomecenterapp\DefaultIcon]
@="coreres.dll,-20797"
[HKEY_CLASSES_ROOT\welcomecenterapp\SelectIcon]
@="coreres.dll,-20798"
[HKEY_LOCAL_MACHINE\ControlPanel\WelcomeCenter]
"Redirect"=":MSWELCOMECENTER"
[HKEY_LOCAL_MACHINE\System\WelcomeCenter]
"CmdLine"=""
[HKEY_LOCAL_MACHINE\ControlPanel\WelcomeCenter]
"Group"=dword:1
hope you can help...
I'am at the end...
I think WM'Reloc is not compatible with my device ???
Thanks
Everal

everal said:
I'am at the end...
I think WM'Reloc is not compatible with my device ???
Click to expand...
Click to collapse
I had issues with it as well. I had to go back to using g'reloc.

hey guys any solution to this problem? I've been facing it on my Samsung i780.. damn this won't move past the Windows mobile logo.. yet it plays the welcome screen sound.. what a shame..

chef raven,
not trying to hijack your thread but can you please answer my PM.
i've been waiting for weeks now.
thanks

Stripping oem into ext

Hello everyone,
Can anyone strip down the oem folder of opal to ext like done in newer devices official roms. Please can anyone do it ?. If no one has enough time atlest someone guide me how to do that.
Custom oem:http://www.mediafire.com/?zojnnyznzvm
Official rom:http://rapidshare.com/files/1487199...1_infineongsm4.1.13.66_03.29.90_Ship.exe.html
You can choose anyone either the custom oem to strip or extract oem from official rom and then work on.
Plz this is a request

Hi!
Just use Cab_Converter for your problem. http://forum.xda-developers.com/showthread.php?t=525302&highlight=Cab+Converter
It can convert *.cab into OEM packages and OEM's into EXT packages.
Its not realy difficult, download and extract the files to c:\CAB_Converter\
EDIT: Oh Sorry, OEM to EXT is coming soon

sandman01 said:
Hi!
Just use Cab_Converter for your problem. http://forum.xda-developers.com/showthread.php?t=525302&highlight=Cab+Converter
It can convert *.cab into OEM packages and OEM's into EXT packages.
Its not realy difficult, download and extract the files to c:\CAB_Converter\
EDIT: Oh Sorry, OEM to EXT is coming soon
Click to expand...
Click to collapse
Thanks for the reply. But i dont wanna covert cab files i wanna do like in latest htc official rom releases like in official wm 6.5 upgrades for diamond 2 (topaz) etc in oem app and oem lang 0409 all files are coverted to ext except a few.

However, if you only want to get the EXT packages out of the official rom, you can use visual kitchn and dump the *.nbh file.
the kitchen will create the files for you.
I will upload the Packages for you in a few minues!
Edit:
http://rapidshare.com/files/329631677/Opal_External_Packages.rar.html
MD5: C973B323C8DC693EAEB64DA232C985C3

sandman01 said:
However, if you only want to get the EXT packages out of the official rom, you can use visual kitchn and dump the *.nbh file.
the kitchen will create the files for you.
I will upload the Packages for you in a few minues!
Edit:
http://rapidshare.com/files/329631677/Opal_External_Packages.rar.html
MD5: C973B323C8DC693EAEB64DA232C985C3
Click to expand...
Click to collapse
So nice of u that u done it for me. But bro i really dont want that i have that what i mean is u have downloaded that official rom in and dumped now see the oem in that go to oem apps. You will see one dsm and many app. Now compare that with oem of mega or topaz wm 6.5 or latest jade rom. You will see in all of them that app which are present in oem app are coverted to ext packages. The same i want to do with the oem app of opal. I hope u understood . Didnt? ok see ur pm.

OK, now I think I know what you mean.
My english is so bad so it taes some time to understand.
you would like to create EXT pakages from the application located in the OEM\OPAL\COMMON\OEMApps folder.
These programs are not device or resolution specific. (as far as I know)
so you can delete the files and include EXT packages from newer roms in you EXT folder.
I see there is a AutoRun, CommManager,...
These files are realy old, so it would be an improovement if you have a RunCC and a new CommManager, from the latest builds
Thats just an example.
However, I will also search for an Tool which can convert the files and programs out of the OEM folder to EXT packages.

sandman01 said:
OK, now I think I know what you mean.
My english is so bad so it taes some time to understand.
you would like to create EXT pakages from the application located in the OEM\OPAL\COMMON\OEMApps folder.
These programs are not device or resolution specific. (as far as I know)
so you can delete the files and include EXT packages from newer roms in you EXT folder.
I see there is a AutoRun, CommManager,...
These files are realy old, so it would be an improovement if you have a RunCC and a new CommManager, from the latest builds
Thats just an example.
However, I will also search for an Tool which can convert the files and programs out of the OEM folder to EXT packages.
Click to expand...
Click to collapse
Buddy no ur english is not bad actually many out there didnt understood me. Thanks for ur interest in my question. Actually i tried what u suggested above but for what purpose i want to do this didnt cleared that is i wanted to fix one problem. But np another member kilzone is working on it .

I haven't tested the tool yet, but maybe this could help you!
http://forum.xda-developers.com/showthread.php?t=561405
Here is also an interresting thread about converting tools:
http://www.everythingdiamond.info/showthread.php?t=1415&page=3

Bro its solved kilzone made that for me.