Related
Does anyone have this WM5 smart dial... :?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(capture from http://www.buzzdev.net/index.php?option=com_simpleboard&Itemid=59>&func=view&catid=36&id=9738#9738)
This Smart Dialing or InteliDial looks working on WM2005....
mwilmar said:
Does anyone have this WM5 smart dial...
Click to expand...
Click to collapse
Almost .... mine is on a Magician II and it's Version 2.2 (Build 21527) but not the black that you have - it's all T-Mobile colours.
brykins said:
mwilmar said:
Does anyone have this WM5 smart dial...
Click to expand...
Click to collapse
Almost .... mine is on a Magician II and it's Version 2.2 (Build 21527) but not the black that you have - it's all T-Mobile colours.
Click to expand...
Click to collapse
Can u post it..? i need 2 test it on WM5.... plz :?
Yes, please share it. Thanks.
mwilmar said:
Can u post it..? i need 2 test it on WM5.... plz :?
Click to expand...
Click to collapse
It'll be one of the files in the EXT_ROM which is in the Uploads/Charmer section of the ftp site.
brykins said:
mwilmar said:
Can u post it..? i need 2 test it on WM5.... plz :?
Click to expand...
Click to collapse
It'll be one of the files in the EXT_ROM which is in the Uploads/Charmer section of the ftp site.
Click to expand...
Click to collapse
Thanks brykins, I found 1 file inside the path named 'smartdialing enable....cab' but nothing happen after installed. It's seems no more cab files seems like about smartdailing stuff.
Any idea? Or something built in the rom?
siukeung said:
Thanks brykins, I found 1 file inside the path named 'smartdialing enable....cab' but nothing happen after installed. It's seems no more cab files seems like about smartdailing stuff.
Any idea? Or something built in the rom?
Click to expand...
Click to collapse
No idea....I'm probably going to hard reset later today and re-install now that I know what software I am using on WM5, so I'll see what of the EXT_ROM I install and what one gives the dialer.
me! said:
re-install now that I know what software I am using on WM5, so I'll see what of the EXT_ROM I install and what one gives the dialer.
Click to expand...
Click to collapse
Okay - have reset and installed:
CAB: \Extended_ROM\CAB-Customization-Connection-TMUK-Charmer-Nov15.sa.CAB - Add T-Mobile Internet Settings
CAB: \Extended_ROM\Signed_EnableATAbortSTKCall.sa.CAB - enables ATAbortSTKCall
CAB: \Extended_ROM\Signed_GPRS_PAP.CAB - changes default GPRS auth to PAP
CAB: \Extended_ROM\SmartDialing_enable_0915_signed.CAB - enables smartdialling
And also the extracted soft-key customising menus and everything works fine. I think these are about the minimum that needs to be installed from the T-Mobile EXT_ROM
brykins said:
me! said:
re-install now that I know what software I am using on WM5, so I'll see what of the EXT_ROM I install and what one gives the dialer.
Click to expand...
Click to collapse
Okay - have reset and installed:
CAB: \Extended_ROM\CAB-Customization-Connection-TMUK-Charmer-Nov15.sa.CAB - Add T-Mobile Internet Settings
CAB: \Extended_ROM\Signed_EnableATAbortSTKCall.sa.CAB - enables ATAbortSTKCall
CAB: \Extended_ROM\Signed_GPRS_PAP.CAB - changes default GPRS auth to PAP
CAB: \Extended_ROM\SmartDialing_enable_0915_signed.CAB - enables smartdialling
And also the extracted soft-key customising menus and everything works fine. I think these are about the minimum that needs to be installed from the T-Mobile EXT_ROM
Click to expand...
Click to collapse
that SmartDialing_enable_0915_signed.CAB only content of this XML... :
<wap-provisioningdoc>
<characteristic type="FileOperation">
<characteristic type="\Windows\Help\Smart Dialing.lnk" translation="install" >
<characteristic type="Shortcut">
<parm name="Source"
value="\Windows\IntelliDialer.htm" translation="install"/>
</characteristic>
</characteristic>
</characteristic>
<characteristic type="Registry">
<characteristic type="HKLM\Security\Phone\Skin" translation="filesystem" >
<parm name="ext" datatype="string" value="\windows\phcanhtc.dll" translation="filesystem" />
</characteristic>
<characteristic type="HKCR\CLSID\{1AD110A1-B3E6-4CB9-AC0F-69E059AFBFEF}" translation="filesystem" >
</characteristic>
<characteristic type="HKCR\CLSID\{1AD110A1-B3E6-4CB9-AC0F-69E059AFBFEF}\InprocServer32" translation="filesystem" >
<parm name="Default" datatype="string" value="DPadMenu.dll" translation="filesystem" />
</characteristic>
<characteristic type="HKLM\SOFTWARE\Microsoft\Shell\Extensions\ContextMenus\Phone" translation="filesystem" >
</characteristic>
<characteristic type="HKLM\SOFTWARE\Microsoft\Shell\Extensions\ContextMenus\Phone\MSCdial" translation="filesystem" >
</characteristic>
<characteristic type="HKLM\SOFTWARE\Microsoft\Shell\Extensions\ContextMenus\Phone\MSCdial\{1AD110A1-B3E6-4CB9-AC0F-69E059AFBFEF}" translation="filesystem" >
<parm name="Default" datatype="string" value="" translation="filesystem" />
</characteristic>
<characteristic type="HKCR\CLSID\{7CB99F67-9930-4375-919C-37512108F0C3}" translation="filesystem" >
</characteristic>
<characteristic type="HKCR\CLSID\{7CB99F67-9930-4375-919C-37512108F0C3}\InprocServer32" translation="filesystem" >
<parm name="Default" datatype="string" value="DPadMenu.dll" translation="filesystem" />
</characteristic>
<characteristic type="HKLM\SOFTWARE\Microsoft\Shell\Extensions\ContextMenus" translation="filesystem" >
</characteristic>
<characteristic type="HKLM\SOFTWARE\Microsoft\Shell\Extensions\ContextMenus\Phone" translation="filesystem" >
</characteristic>
<characteristic type="HKLM\SOFTWARE\Microsoft\Shell\Extensions\ContextMenus\Phone\MSCProg" translation="filesystem" >
</characteristic>
<characteristic type="HKLM\SOFTWARE\Microsoft\Shell\Extensions\ContextMenus\Phone\MSCProg\{7CB99F67-9930-4375-919C-37512108F0C3}" translation="filesystem" >
<parm name="Default" datatype="string" value="" translation="filesystem" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
It look's like they need intellidialer too...
dopod 818 pro cabs in ext rom any help?
I recently upgraded to the prophet. There is smart dialing available. But it seems the prog is embedded in the OS, or maybe another hidden extrom?
I unlocked my extrom and it is listed as Extrom2. This is about 10MB. The files in Extrom2 are mostly autoconfig cabs for all the different telcos. Plus voice commander & several customization cabs. Only a 70K cab smart-dialing enable cab, no other smart dialing cabs.
the dopod pro has 47+MB storage space available plus the 10mb extrom1 is only 57MB. Plus the WM5.0 OS, which is about 32MB gives 89MB. Where is the rest? We have 128MB ROM. Eten M600 has 80+MB available space. I'm missing about 39MB somewhere. Could it be there's an ExtRom 1? Any gurus can shed some light here? If anyone can help, I'd be glad to post the smartdialling cab here as I also have an xda2 running wm5.0 with no smartdialling
818 Pro - Chinese Version with NO Intellidialer.....
Please help, my chinese version 818 Pro has no intellidialer built-in.
Can anybody extract it from an English version?
Looking at the contents of the XML file in the SmartDialing_enable CAB posted by mwilmar......it looks like in addition to the SmarDialing_enable CAB file, you also need to get copies IntelliDialer.htm and DPadMenu.dll from the \Windows directory of someone with the 2.2 version of Smart Dialing.
Try copying all 3 files (the CAB file, IntelliDialer.htm and DPadMenu.dll) into your WM5 \Windows directory. Then tap on the CAB file which will hopefully update the registry with the necessary settings.
If anyone can get me those files, I'm happy to try on my XDA Atom.
ozmael said:
Looking at the contents of the XML file in the SmartDialing_enable CAB posted by mwilmar......it looks like in addition to the SmarDialing_enable CAB file, you also need to get copies IntelliDialer.htm and DPadMenu.dll from the \Windows directory of someone with the 2.2 version of Smart Dialing.
Try copying all 3 files (the CAB file, IntelliDialer.htm and DPadMenu.dll) into your WM5 \Windows directory. Then tap on the CAB file which will hopefully update the registry with the necessary settings.
If anyone can get me those files, I'm happy to try on my XDA Atom.
Click to expand...
Click to collapse
Try this thread for the files you are after
http://www.buzzdev.net/index.php?option=com_simpleboard&Itemid=59&func=view&catid=45&id=10251#10251
Let us know if you get it working on the Atom.
Re: dopod 818 pro cabs in ext rom any help?
Putra said:
I recently upgraded to the prophet. There is smart dialing available. But it seems the prog is embedded in the OS, or maybe another hidden extrom?
I unlocked my extrom and it is listed as Extrom2. This is about 10MB. The files in Extrom2 are mostly autoconfig cabs for all the different telcos. Plus voice commander & several customization cabs. Only a 70K cab smart-dialing enable cab, no other smart dialing cabs.
the dopod pro has 47+MB storage space available plus the 10mb extrom1 is only 57MB. Plus the WM5.0 OS, which is about 32MB gives 89MB. Where is the rest? We have 128MB ROM. Eten M600 has 80+MB available space. I'm missing about 39MB somewhere. Could it be there's an ExtRom 1? Any gurus can shed some light here? If anyone can help, I'd be glad to post the smartdialling cab here as I also have an xda2 running wm5.0 with no smartdialling
Click to expand...
Click to collapse
Just tried to alter the config.txt inside the ExtRom2, after a soft-reset, the Text file restored to its initial content, all my alterations had gone.
Seems that there really a ExtRom "1" stuff, ExtRom2 is just like a temperory storage.
And, had tried to use the Rom unlocker
http://www.pxdxa.com/read.php?tid=8272&keyword=ext rom
after running the unlocker, it told me to "Unlock ExtRom First"!! So, there should be an ExtRom, but cannot be easily exposed. still trying ....
I need the Smartdialer too, has an Eng version 818Pro Rom in hand now, it has Smartdialer built-in.
Zelig said:
ozmael said:
Looking at the contents of the XML file in the SmartDialing_enable CAB posted by mwilmar......it looks like in addition to the SmarDialing_enable CAB file, you also need to get copies IntelliDialer.htm and DPadMenu.dll from the \Windows directory of someone with the 2.2 version of Smart Dialing.
Try copying all 3 files (the CAB file, IntelliDialer.htm and DPadMenu.dll) into your WM5 \Windows directory. Then tap on the CAB file which will hopefully update the registry with the necessary settings.
If anyone can get me those files, I'm happy to try on my XDA Atom.
Click to expand...
Click to collapse
I tried this on my PPC-6700 just to see if it would work and it did not add Smartdialing for me. I copied the 3 files shown above into the Windows folder and I then ran the cab. After the cab installed I checked the dialer app to see if the smartdialing option was there and it was not. I tried a soft reset and checked again and no joy. Anybody know how to add this feature to my device?
Click to expand...
Click to collapse
Re: dopod 818 pro cabs in ext rom any help?
kfflee said:
Just tried to alter the config.txt inside the ExtRom2, after a soft-reset, the Text file restored to its initial content, all my alterations had gone.
Seems that there really a ExtRom "1" stuff, ExtRom2 is just like a temperory storage.
And, had tried to use the Rom unlocker
http://www.pxdxa.com/read.php?tid=8272&keyword=ext rom
after running the unlocker, it told me to "Unlock ExtRom First"!! So, there should be an ExtRom, but cannot be easily exposed. still trying ....
Click to expand...
Click to collapse
Any gurus can shed light on this ExtRom1 and ExtRom2??
I think the feature is embedded in the phone application,,if we can get the file "cprog.exe" from any working WM5 pocket pc with the smart dial working in it + the button to turn the speaker on in the dial pad also,,,getting this file might get things working (i suppose), I tried to get it out of a K-jam but I couldnt,,maybe if someone have dumped the rom can help us
...
I think that's not in cprog.exe. I have a ROM dumped from Himalaya(1.71.64) and from Wizard(1.3.2.5 CSY). Wizard has SmartDialer,Hima not. I've tried today to scan both registries for any differences about and have found much more keys/values about smartdialing. There are these files with same filesize. Anyway here they are including registry values,that are in Wizard.
Smart dialling for himalaya wm5
dear tomasNM
How to install this intellidialer to himalaya WM5 having ROM VER 1.65b96? Regards.....chandra
...
I want to install and use,but I don't know how. Nothing,that I have tried,isn't working. I am not able alone to port it to the Himalaya WM5 and noone want/unable to help me. Someone?
What I guess it because of wince.nls file. I can find it after flash, but I can't find in folders before I cook them. Do you have any idea?
Another thing is that Reg Table,
mxipupdate_OEMOPERATORS_101.provxml， nian font，default could be：
<!-- ========================= Nina font =========================-->
<characteristic type="Registry">
<characteristictype="HKLM\SYSTEM\GDI" translation="filesystem">
<parm name="FontLinkMethods" datatype="integer"value="1" />
</characteristic>
<characteristictype="HKLM\Software\Microsoft\FontLink\SystemLink" translation="filesystem">
<parm name="Segoe Condensed"datatype="string"value="\Windows\nina_cs.ttf,Nina" translation="filesystem" />
</characteristic>
<characteristictype="HKLM\Software\Microsoft\FontLink\SystemLink" translation="filesystem">
<parm name="Segoe CondensedBold"datatype="string"value="\Windows\ninab_cs.ttf,NinaBold" translation="filesystem" />
</characteristic>
</characteristic>
For Chinese, could be
<!-- ========================= Nina font =========================-->
<characteristic type="Registry">
<characteristictype="HKLM\SYSTEM\GDI" translation="filesystem">
<parm name="FontLinkMethods" datatype="integer"value="1" />
</characteristic>
<characteristictype="HKLM\Software\Microsoft\FontLink\SystemLink" translation="filesystem">
<parm name="Segoe Condensed"datatype="string"value="\Windows\nsimsun.ttf,NSimSun" translation="filesystem" />
</characteristic>
<characteristictype="HKLM\Software\Microsoft\FontLink\SystemLink" translation="filesystem">
<parm name="Segoe Condensed Bold"datatype="string"value="\Windows\nsimsun.ttf,NSimSun" translation="filesystem" />
</characteristic>
<characteristictype="HKLM\Software\Microsoft\FontLink\SystemLink" translation="filesystem">
<parm name="Tahoma"datatype="string"value="\Windows\nsimsun.ttf,NSimSun" translation="filesystem" />
</characteristic>
<characteristictype="HKLM\Software\Microsoft\FontLink\SystemLink" translation="filesystem">
<parm name="Courier New"datatype="string"value="\Windows\nsimsun.ttf,NSimSun" translation="filesystem" />
</characteristic>
<characteristictype="HKLM\Software\Microsoft\FontLink\SystemLink" translation="filesystem">
<parm name="Nina"datatype="string"value="\Windows\nsimsun.ttf,NSimSun" translation="filesystem" />
</characteristic>
<characteristictype="HKLM\Software\Microsoft\FontLink\SystemLink" translation="filesystem">
<parm name="NSimSun"datatype="string"value="\Windows\nina_cs.ttf,nina" translation="filesystem" />
</characteristic>
</characteristic>
I know that wince.nls is located in the xip part of the rom. I have recently learnt how to replace a file in xip on the Vox.
I m writing this from my phone so unfortunately I can't help much more. I should be able to tomorrow night.
Dr. Martin Gonzo said:
I know that wince.nls is located in the xip part of the rom. I have recently learnt how to replace a file in xip on the Vox.
I m writing this from my phone so unfortunately I can't help much more. I should be able to tomorrow night.
Click to expand...
Click to collapse
Many thanks. It seems to me that every step I did is write, but it still can't display Chinese correctly. I doubt some tools use in compile deos not support far east language.
I haven't really followed your previous attempts. Could you give me a little summary of all what you've tried ?
Do you have an original chinese rom from which I could take the file and try something ? If so please upload somewhere and I'll look at it maybe tomorrow.
Great.
My purpose is to cook my own ROM by using your kitchen.
What I've done are:
1. I was using a vox released by China Mobile, it has two localized languages, Chinese and English. The OS version is is CE OS 5.2.1236.
2. by using pdocread.exe -l,
pdocread -w -d DSK1: -p Part02 -t
pdocread -w -d DSK1: -p Part02 0 0x3528000 Part02.raw
pdocread -w -d DSK1: -p Part01 0 0x391800 Part01.raw
pdocread -w -d DSK1: -p Part00 0 0x217400 Part00.raw
I got 3 raw files.
2. by using prepare_imgfs.exe Part02.raw -nosplit
I got 2 bin files, imgfs_raw_data.bin
imgfs_removed_data.bin
3. by using viewimgfs.exe imgfs_raw_data.bin
I got a dump directory, which should contain all the files from part02.raw
4. by using package_tool，ie, PKGTool.exe
I sorted files in dump directory into 2 folders, OEM and SYS
5. I pick out Chinese language components from OEM and SYS folders and uploaded to XDA ftp.
6. frauhottelmann helped me to compile them into 804 Chinese language package.
Pls refer http://forum.xda-developers.com/showthread.php?t=366143
ftp://ftp.xda-developers.com:21//Uploads/Smartphone/Vox/Vox Kitchen 0.3/languages/804 Chinese.exe
7. by using kitchen released by you and frauhottelmann, I am trying to build my own ROM.
(1) copying files extracted from 804_Chinese.exe to related folders into the kitchen
(2) following the intructions, cooked the ROM and flash the device
(3) the result is that English can display correctly, but Chinese charaters display in squares
8. I have checked device after flashed:
(1) Chinese font is same as it in China mobile version
(2) Wince.nls file is same as it in China mobile version
(3) Related registration key are correct.
(4) Just can't display Chinese correctly.
9. I have also used the kitchen by another way:
(1) Copying the dump directory got from step 3 above into the blank temp folder in kitchen
(2) Start step 3 "Build", ignor steps G'Reloc and Build OS, directly start step 3 "Creat ROM"
(3) No error report came out and got NBH file smoothly
(4) Flash the device smoothly
(5) Display Chinese as it is, very good though there some shortcuts and catelogues are missing or twisted.
My question is how can I use your kithen to cook a rom that can display Chinese correctly.
One more thing I discoverd from Chinese fans is that the rgucom.exe problem. Some fans said that rgucom.exe is not compitable with far east lanaguages and made a modified version (Please refer the attachement, pls delete .zip and then extract it). I don't know. I changed this file and cooked again. Problem was still there.
Could you also upload part0 and part1 of your chinese rom ?
I'll try something tonight.
But I must say I don't really know why what you did in (9) produced a rom that could display chinese text whithout modifying xip. Or maybe your chinese language pack misses some important files.
I'm sure we'll get somethin working as soon as I'm back home.
Sorry for I am using different ID since my ID iQQ is not allowed to post after I changed my email address in profile.
Here you can got all the 3 raw files.
ftp://xda:[email protected]:21//Smartphone/Vox/ROMs/dopodchina/dopodvoxmainlandchina.zip
OK, I got myself back.
Please notice that, when I am using the dumped directory to repack it, I did not use the par00.raw and parto1.raw since I even don't know how to extract them.
You may refer the Singapore ROM, which contains English and Chinese, but they put the English in first priority.
http://www.dopodasia.com/download/RUU_Vox_DOPODASIA_WWE_1.19.707.3_4.1.13.37_02.83.90_Ship.exe
Ok I tried playing à lot with the xip to replace wince.nls and mxip_lang.vol but no matter what I do the phone will always get stuck on first splashscreen... it seems the xip gets too big to be reintegrated to the rom. wince.nls is really bigger and I guess that when modifying xip every ko counts. So anyway your only chance of cooking seems to start from scratch with one of the roms you sent me but you won't have the latest version... or if htc has released à 1.34 for chinese language then you should extract windows.nb from it and use it in the kitchen. it would probably work.
Got it. Thanks a lot. I'll try and let you know.
By the way, do you have any idea how to use the 3 raw files flash back to the device?
By your hits. I copy the mxip_lang.vol from Chinese version into XIP folder (replace), then build, then flash. All steps are really smooth. Then I still got wrong language display.
Then I intalled the attached file, Chinese display comes out! However, when I try to change the path of fonts into \Winodws, rather then \Windows\Fonts, the display goes wrong again.
Remind: After you flash, the first boot will take longer time. I guess what you said "stuck" is not real.
Thanks.
Post an attachement is really hard here. I uploaded it at:
ftp://xda:[email protected]:21//Smartphone/Vox/from iQQ/UK_WM6CN_core.cab
putting mxip_lang.vol into XIP folder doesn't actually replace the xip. I think this folder is only used by BuildOs for boot.rgu.
Replacing the xip is a little more complicated. The xip is actually your part00.raw and part01.raw files. They can also be extracted from windows.nb
Nad the phone was really stuck first splashsscreen and the display went wrong with some weird lines after some times.
I wonder if we can rebuild a windows.nb file by putting together all the .raw files you dumped ? This way you could rebuild your rom whithout any problem.
I'll look at your file later in the day.
I used your 0.5a as a reference OS.nb and build a rom again. Building process are smooth. After flash, I installed file above. The when open "about", it says error. It can display both Chinese and English correctly, but I can't find "China" in "local".
But when I change the language back to English, the "About" looks good.
Good news. I changed the referece OS.nb to one that extracted from Singapore shiped, then creat OS -> flash.
After flash, Chinese still looks blocks. However, if I import the attaced reg file (pls delete .txt after download), and reboot, Chinese comes our correctly. The about shows that:
CE OS 5.2.1236 (18128.0.4.4)
yes I think that is the only way to do it (using Os.nb extracted from Singapore shiped) but then we mix files from newer rom with an older baserom and I don't know how it will come up on stability.
I'm glad you've find your solution though
Dr. Martin Gonzo said:
yes I think that is the only way to do it (using Os.nb extracted from Singapore shiped) but then we mix files from newer rom with an older baserom and I don't know how it will come up on stability.
I'm glad you've find your solution though
Click to expand...
Click to collapse
Can you please let me know how can I integrate the reg keys into the rom before I create the OS.nb? and
Is there any way to repack the 3 raw files back to a nbh file or using raw files to flash back?
Add the line from the reg file you posted (except REGEDIT4 of course) into the rgu in language_chinese
It should work.
Dr. Martin Gonzo said:
I wonder if we can rebuild a windows.nb file by putting together all the .raw files you dumped ? This way you could rebuild your rom whithout any problem.
Click to expand...
Click to collapse
How can we do that? I am really looking forward to doing this! Thanks!
I don't know if its even possible. I tried "gluing" all the different parts together but this result in a corrupted rom..
Dr. Martin Gonzo said:
Add the line from the reg file you posted (except REGEDIT4 of course) into the rgu in language_chinese
It should work.
Click to expand...
Click to collapse
Thanks. It worked.
hum... i have here a noob question about basic cooking ...
because the lack of roms in my native language... i started to **** my own ...
i have one simple question ...
i now have folders with icons in /programs
and i have a problem,.. how can i arrange the shortcuts in the folders ?
for example.. in packages i edit the "initflashes" and i can change the path of the shortcut to wherever i want...
but how i can change in OEM stuff ? like ACTIVESYNC ? ... i can see the application.exe and the link.lnk em OEM folder... but how can i set the path to the link ?
sry my english ... i dont know if i explained well what i want :\
thanks
Use OEMizer, it's very helpful to create shortcuts.
The simplest way is to modify customization script in OperatorPKG (OEM folder) i think.
I do it this way.
Add to config_operator.txt this line:
XML: \WINDOWS\your_xml.xml
And now create your own XML with description of operations you would like to do.
Examples
Move shortcut:
Code:
<characteristic type="FileOperation">
<characteristic type="\Windows\Nabídka Start\Programy\Nástroje" translation="install">
<characteristic type="MakeDir"/>
</characteristic>
<characteristic type="\Windows\Nabídka Start\Programy\Nástroje\Správce SIM.lnk" translation="install">
<characteristic type="Copy">
<parm name="Source" value="\Windows\Nabídka Start\Programy\Správce SIM.lnk" translation="install"/>
</characteristic>
</characteristic>
<characteristic type="\Windows\Nabídka Start\Programy\Správce SIM.lnk" translation="install">
<characteristic type="Delete">
<parm name="ForceDelete"/>
</characteristic>
</characteristic>
</characteristic>
Change registry values:
Code:
<characteristic type="Registry">
<characteristic type="HKLM\Software\Microsoft\Today" translation="filesystem" >
<parm name="Date" datatype="integer" value="1" />
<parm name="Enabled" datatype="integer" value="1" />
</characteristic>
</characteristic>
thanks for the quick reply!!! ill try
ruizit0 said:
thanks for the quick reply!!! ill try
Click to expand...
Click to collapse
i think have better solution.. go to the oem after to oem lang 409
and open with notepad the initflashfiles.dat
and change or see how make shortcuts..
Yes... But it's possible only in english ROMs.
For example in my Czech rom initflashfiles.dat looks strange...
b16b said:
i think have better solution.. go to the oem after to oem lang 409
and open with notepad the initflashfiles.dat
and change or see how make shortcuts..
Click to expand...
Click to collapse
If you do this, remember to hex edit the file to delete the first two keys on the top left.
b16b said:
i think have better solution.. go to the oem after to oem lang 409
and open with notepad the initflashfiles.dat
and change or see how make shortcuts..
Click to expand...
Click to collapse
dont know why but... i dont have that file lol
im working on this rom
RUU_Kaiser_HTC_PTG_3.28.410.0_radio_sign_25.83.40.02_1.65.17.56_Ship
maybe because its an old release ... (but its the only release in my native language )
ill try the custom .XML trick
the OEMizer is a nice tool ... but i think its only to create new shortcuts right ?
what i want to do is to move the existent shortcuts in OEM to inside my folders...
its possible that OEMizer make that to... but for now ill try the custom solution...
thanks all
used OEMizer... i figured out how it works ... i just get duplicated shortcuts... but its easy to fix... just have to remove the shortcuts in oemapps ...
but i saw now that i have another problem in this field..
because my native language (portuguese) have special charecters like: ã , ç , á .. etc...
when i created the folders..
Directory("\Windows\Menu Iniciar\Programas\Aplicações"):-File("icon.lnk","\Windows\icon.lnk")
Click to expand...
Click to collapse
the special characters doesnt appear :\ ...
Aplicações -> Aplicaes
errr ... isnt possible to make special charecters in initflashes to create the folders ?
thanks
You must have initflashfiles.dat in your kitchen. But it's hidden. You must set up the file manager to "show hidden and system files".
About special characters... You must save result in UTF-16 LE encoding.
N3o21 said:
You must have initflashfiles.dat in your kitchen. But it's hidden. You must set up the file manager to "show hidden and system files".
About special characters... You must save result in UTF-16 LE encoding.
Click to expand...
Click to collapse
hum... i have allways "show hidden and system files" in explorer
but when i get home ill do an dos attrib to double check ...
in the bed .. i remembered that enconding option.. (here is UTF-8) .. ill try later .. hope that isnt a initflashes limitation in special characters
one more question ... i used OEMizer to make some shortcuts for OEM stuff like ActiveSync and others... but the icons dont show up ... hum.. i read something before about that problem but i cant find it :\
(i was thinking that would be great if someone can make an "noob" FAQ for cooking with this little questions to help the people that is starting in the cooking buisness)
Faria once created a nice tutorial on how to cook those things. I think I have the link in the Hermes Kitchen link down in my sign. Check that out!
cant find :\
http://forum.xda-developers.com/showpost.php?p=2357462&postcount=4
there is kaiser ptg rom - dump it and u will get all ptg oem
kareem9nba said:
If you do this, remember to hex edit the file to delete the first two keys on the top left.
Click to expand...
Click to collapse
i never do this and i don't have problem
Hello,
I have a question.
For a answer i already looked around at the net and have read some threads at xda, modaco, and some site at msdn.
The short version: how do i remove a dir from the register with a .xml file?
The long version:
I need to remove a dir from the registry.
I opened a new text document and saved it as _setup.xml.
In this .xml file i wrote:
<characteristic type="Registry">
<nocharacteristic type="HKLM\Software\Microsoft\Shell\DeviceBeta" />
</characteristic>
</characteristic>
After that i opened Quickcab in the first field I put in by application name 1 and by owner 1.
By the second screen I add the _setup.xml file to the windows folder
At the next screen i do nothing and click on create.
I save it as _setup.cab.
After the .cab file is maked i move it to my phone and run it from my phone.
It says that evreything is installed and so on.
But when i reboot my device nothing happened and the dir. at the register is still there.
What am i doing wrong?
Do i need to put something more in the .cab file?
Moved as not ROM Development.
don't think you really understand xml
http://en.wikipedia.org/wiki/XML
xml can't do anything at all on it's own it's a model language which needs to be interpreted by another program
it's not a programming or batch language
Hi,
I believe your xml file should look somthing like this:
To delete a value:
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<!-- Delete a registry value under the following key -->
<characteristic type="HKCU\Software\Second Test Key">
<noparm name="Value To Delete" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
To delete a key (or a dir as you call it):
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<!-- Delete a registry key, with all its values and subkeys -->
<nocharacteristic type="HKLM\Software\RegKey To Delete" />
</characteristic>
</wap-provisioningdoc>
Cheers,
/Cacti
Rudegar said:
don't think you really understand xml
http://en.wikipedia.org/wiki/XML
xml can't do anything at all on it's own it's a model language which needs to be interpreted by another program
it's not a programming or batch language
Click to expand...
Click to collapse
Thank you for the link Rudegar more brain food my brains are already at the point to explode.
One of the threads that i have read is http://forum.xda-developers.com/newreply.php?do=newreply&p=5908996.
Thank you for helping.
le_cactus said:
Hi,
I believe your xml file should look somthing like this:
To delete a value:
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<!-- Delete a registry value under the following key -->
<characteristic type="HKCU\Software\Second Test Key">
<noparm name="Value To Delete" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
To delete a key (or a dir as you call it):
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<!-- Delete a registry key, with all its values and subkeys -->
<nocharacteristic type="HKLM\Software\RegKey To Delete" />
</characteristic>
</wap-provisioningdoc>
Cheers,
/Cacti
Click to expand...
Click to collapse
le_cactus thank you for helping out i am trying this out tonight or tomorrow.
Can i save this in a text file and save it as .xml and then cab it?
Can some one explain how to delete a key in the registry of windows mobile 6.5 by a simple guide ?
Because I am busy making my own rom.
The problem i have is that in the right corner below i have standing I quote: Beta Expires: 05/01/2010
I know you can delete this by going in you registry to hklm/software/microsoft/shell/Devicebeta and delete this key.
But i like to delete this key automatic when i have flashed the rom and not doing it afterwards by going in to the registry.
If i have a problem i try to solving it at my own by reading threads and searching the net for answers but some times i need some help to get it right and to get me on the right track.
I appreciate the help that i get here so thank you all for helping out.
xml to reg and vice versa
First it started for me when I saw an UC capable ROM, from there I too wanted to go from reg/rgu to xml and vice versa After some researching I found several threads concerning my wishes. Within these threads you'll find your desired utilties For the overall clarity I'll start with the beginning;
[App] ROM Flashing Junkies: User Customization is here!
http://forum.xda-developers.com/showthread.php?t=366337
see the UC related software tools
Within this thread there is an application called SDConfig creator which was created by DoeDoe's. Currently it is replaced by;
[Release] UC ROM SDConfig.txt Builder (reborn) [Prikolchik Ed.]
http://forum.xda-developers.com/showthread.php?t=390846
I'm using PHM Registry Editor it allows me to do the following tasks:
Explore the registry to find the operating system and applications configuration,
modify system and applications tweeks not available from the standard options screens,
export all or parts of the registry to .reg files,
backup and restore the complete registry and
perform search on the registry data
Have fun everyone with editing/creating/modifying/wrecking,
Senax
Hello
I bumped into problems when I tried to make a provxml file which would modify the directory structure and/or change the link names inside StartMenu\Programs folder.
I wrote whole long provxml script using some found tutorials, then I put the provxml as _setup.xml inside a CAB file (with a Windows XP makecab.exe). But every time I try to run the CAB on the device I have the error that Installation unsuccessful because of too small rights to install.
I also try to run the provxml directly via CeRegEditor, but it gives me the "Access Denied" communicate.
Then I tried to shorten the provxml because I thought I made some mistake in the script itself, but even when I try to the following very simple script to create one single folder and copy a link to this folder without even changing it's name, it still gives me the same rights error:
Code:
<wap-provisioningdoc>
<characteristic type="FileOperation">
<characteristic type="\Windows\Start Menu\Programs\Narzędzia" translation="install">
<characteristic type="MakeDir" />
<characteristic type="PIM Backup.lnk">
<characteristic type="Copy">
<parm name="Source" value="%CE11%\Tools\PIM Backup.lnk" translation="install"/>
</characteristic>
</characteristic>
</characteristic>
</characteristic>
</wap-provisioningdoc>
Do I need any special certificate to be able to modify the folders/files in StartMenu? I can do it without problems using Total Commander, but I want to make it more "automatic" after flash or HR.
I tried to use MortScript, and it worked fine, but in order to run the script I have to install MortScript application first. And I want to avoid installing any unnecessary software as Jackos ROMs are clean as a teardrop...
Thanks in advance for any help