I had a hard time to upgrade and modify my xda2 so I decided to make a small tutorial for everyone with the information’s I found on the forum. It’s not perfect but it could help.
Thank's to every one who made all this possible!!
Before starting I recommend every one to make a back-up of your rom
http://forum.xda-developers.com/viewtopic.php?t=4608
1- Extended Rom:
Your XDA2 has an Invisible Extended Rom in the device containing the operator’s configuration files and software.
Modifying it will allow you to customize the boot image and to choose the programs you wish to install during the setup of the device.
To show the extended rom on your device your need to apply this small hack and then open your file explorer:
http://www.ppcw.net/index.php?itemid=1638
2- Files contained in the Extend Rom:
Broadcast_WWE.sa.CAB:
Seems to only set the CellBroadcast setting to enabled or disabled. (I guess this refers to the Reception of News via SMS by selecting channels of interested. Quite expensive I think and only interesting for phones that do not have any other capabilities of receiving and displaying information).
T-Mobile NL sets it on, with O2 it's switched off.
CallerIDRC11_WWE_1.5.sa.CAB:
Installs the CallerID application from IA Style and the Photo Contacts extension. There are other programs that are able to provide this functionality but I use it.
CameraRC131_WWE_1.5.sa.CAB:
The camera application for taking pictures and recording videos. AFAIK there is currently no alternative to this one, you should leave it in your ROM.
GPRSMonitor_WWE.sa.CAB:
Includes the GPRS Monitor from SPB Soft. Very useful I would recommend it unless you aren't going to use GPRS anyway.
MIDI56.sa.CAB:
RingTone plugin player. Allow you to play back RingTones in the following formats: mid,3gp,mp4. Also seems to register the audio/midi MIME type for playback of midi files directly from Internet Explorer.
By default the XDA can play back only wav and wma audio files (AFAIK)
MMS1507_WWE.sa.CAB:
Installs the Arcsoft MMS application for composing and sending MMS messages.
VideoMMS.sa.CAB (not contained in Qtek):
Installs the "Video MMS.exe" file into the Windows folder. When you start it you are in camera mode immediately and after you have recorded a picture or video you get into MMS composition mode.
This seems to be just an easier way to compose MMS messages since the main MMS Application (see above) is already able to compose MMS messages.
OEM_AKU1_WWE_4AP.sa.CAB (named OEM_4AP_WWE.CAB in Qtek ROM)
Installs the following files: GPRSAuthentication.exe, BTSetting.exe, STK.exe and WModem.exe
I am not sure if these are customized versions or if the normal ROM doesn't contain them. Well perhaps not because these are specific to the Phone edition so they can't be present in the main ROM, maybe they are contained in the Radio ROM, but probably they are only contained here, meaning you shouldn't remove this cab file.
OEM_WWE_03120301.sa.CAB (named OEM_WWE_03122301.sa.CAB in Qtek ROM)
Installs files for Bluetooth: AudioGW.dll, BthASPlugIn.dll, rilgsm.dll, Serial3.dll and Wavedev.dll. Also contains the new feature of mapping a (dynamic) serial port for BT.
I think you should not remove it.
TM_phone_class10.CAB (not contained in Qtek):
Installs several registry settings regarding phone functionality. (See my other post regarding this topic: http://forum.xda-developers.com/viewtopic.php?t=5539)
TMCOMREG.sa.CAB (not contained in Qtek):
Contains some of the settings contained in the previous one anyway. I'm not sure if it does anything else but I don't think so.
TMD_AP_NL.sa.CAB (not contained in Qtek):
Implements several settings specific to T-Mobile (NL): Restricts video types for MMS. Adds connection and gateway settings for MMS connection via T-Mobile NL. Adds a T-Mobile profile to GPRS Monitor.
I would not install this cab unless you live in NL!
TMD_NL.sa.CAB (not contained in Qtek):
Sets the HKEY_LOCAL_MACHINE\SOFTWARE\OEM\3rdversion\MSYSTEM1 value to the provider name.
Not required!
TMDNLCustomize.sa.CAB (not contained in Qtek):
Adjusts all the "theming" stuff: Changes colors, installs Today-theme, installs T-Mobile Dialpad, sets T-Mobile ringtone.
If you don't like you xda2 look like a pink pig you should leave this out.
(You can extract single items from the cab file if you like)
t-mobile_shortcuts_only(UK).PPC2002_ARM.CAB (not contained in Qtek):
Contains some strange things that seem to me rather useless: "WebDisplayText t-zones", "T-Mobile Resetter.exe", "T-Mobile PIE Launcher.exe", "TMobileWebToday.dll", "T-Mobile Homepage Plugin".
I wouldn't install this one!
Version_AKU1.sa.CAB (Version_AKU1_160.sa.CAB in Qtek):
Seems to only set the version number of the extended ROM in the registry.
3- Modifying and editing your Extended Rom:
Most of the latest XDA2 have a write protected Extended Rom
A) For NOT Write Protected Extended Rom:
If your XDA2 Extended Rom is not write protected just add the new files you want, you can find on the forum many different extend rom files (O2, T_Mobile, Orange) and kitchen your own extended Rom by adding the cab files directly in the Extended_rom directory and soft reset.
B) For Write Protected Extended Rom:
The only way for the moment (until we find a way to make the rom writable) is to use the upgrade programs used by the operators and ER2003Edit program.
1)- Download
http://www.c1au.com/iMatePDAROMS/ruu15283.zip
or
http://www.clubimate.com/Support/ruu113sku1.zip
2) Simply unpack the complete T-Mobile Rom update file (it's a zipped EXE) into a folder.
There you will find these 6 files:
- HimaClearJumpCode.exe
- HimaGetDeviceData.exe
- HimaUpgradeUt.exe
- ms_.nbf <----- this is the file which holds Ext Rom!
- NK.nbf (main rom)
- Radio_.nbf (radio rom)
3) Delete the other *.nbf files to prevent updating the full XDA2/MDA2 rom. You only need "ms_.nbf" and the "*.exe" files!
4) Now modify the ms_.nbf with the tool softworkz kindly provided.
http://wiki.xda-developers.com/wiki/ER2003Edit
5) After this, install the modified ext-rom to your XDA2/MDA2 by starting "HimaUpgradeUt.exe" and follow the instructions!
6) If you get a country code error during the install you will need to modify the country code included in the ms_.nbf file
- Download xda2nbftool
http://forum.xda-developers.com/viewtopic.php?t=5563
- Put xda2nbftool.exe in the same folder as your ms_.nbf file
- Run xda2nbftool.exe from Command Prompt and type the following command
xda2nbftool.exe -so O2 -v ms_.nbf
Replace O2 by your operator’s name (ex: orange, O2 etc)
It should now work!
cheers,
Yann
nice one Yann
Thanks
I had a go at doing the "if your extended rom is protected"
I down loaded the file
1)- Download
http://www.c1au.com/iMatePDAROMS/ruu15283.zip
and accidentally ran it.... I know I was stupid... I now have an I-Mate instead of a XDA - O2. Please help can I get the O2 back is there a programme that does the same as the one I just have used. It has changed every thing the radio stack, the other bits of software, I am just pleased it still works of calls.
I couldn’t find the indivuiual HimaUpgradeUt.exe programme any ware.
Please help I am really stuck at the minute!!
The bit I didn’t understand was the bit about unpack the exe. Which I now understand how to do. Although I have upgraded to Rom 1.52.00wwe, radio version 1.06.01, I can haply say I have the original O2 rom back in place with additional programmes installed in the Ex-Rom. I had a fair bit of space so I popped some music files in as well!!!!
Thanks for all the help!!!!
thanks yann for the perfect summary
as newby i needed something clear like this to dare my first rom changes, and i successfully did!
it would be even more perfect if also somehow the program settings/passwords could be cooked in/restored from the extended rom. i searched the forum but could not find any hints.
Are there methods for this ?
Perhaps a silly question, but I'm fairly conservative when it comes to messing around with my device.
How do you find out or know if your Ext ROM is write protected or not? I know that I can add applications to my Ext ROM and it does not seem like I should be able to do that if it's write protected, but then again I'm not sure if this matters.
Ed
ed, if you can copy files to your ext-rom via activesync, it is per definition not write-protected.
your not that conservative, because you already run a tool or edited the registry to be able to see the ext-rom
ronald,
Well I guess you are right I do like to play around, as I get more comfortable doing so. It is this Forum, guys like you, and some other forums that have made this possible for me to do. For some reason I'm more comfortable in general hacking around a desktop pc than a PPC.
I thought my Ext ROM must not be write protected. When I deleted the TMD files, described here as useless, I got the message that they were read only, but they did go away from the Ext ROM Folder. I do not notice a big difference, however, nor did it free up that much memory. I was thinking that I might need to do more then this. Do I?
So basically, if my Ext ROM is not right protected, and I have been already loading programs into the Ext ROM, I’m pretty much at the place people are trying to get with the Ext ROM Cook ER...Edit. Is that correct or am I missing something here?
Ed
Ed,
I do not like flashing rom (or bios) on either my desktop or PDA (if not absolute sure to fix bugs). However flashing the PDA's ext-rom can basically not screw up the PDA because you don't touch the OS, so I flashed the ext-rom to get familiar with the PDA flashing in general (and also to have a restore of my standard used software after a hard-reset).
About your ext-rom; I do not recognise your situation. I would say if it is read-only the file will not disappear (like with my PDA).
I did notice while editing the ext-rom file for flashing that the file is fixed ~16MB, regardless of which cab's are included or deleted.
Maybe this is the same effect that you see when deleting the file in the ext-rom ???????? (although I can imagine both effects have no relation)
ronald
Camera Programs
Okay,
I made a custom ROM with the following programs:
CAB: \Extended_ROM\CameraRC131_WWE_1.5.sa.CAB
CAB: \Extended_ROM\CallerIDRC11_WWE_1.5.sa.CAB
CAB: \Extended_ROM\MMS1507_WWE.sa.CAB
CAB: \Extended_ROM\GPRSMonitor_WWE.sa.CAB
CAB: \Extended_ROM\Version_AKU1.sa.CAB
CAB: \Extended_ROM\OEM_AKU1_WWE_4AP.sa.CAB
CAB: \Extended_ROM\OEM_WWE_03120301.sa.CAB
CAB: \Extended_ROM\VideoMMS.sa.CAB
Awesome, alot less bloat, but.... Camera doesn't work.. Application says Camera is not a valid Pocket PC application. :: grumble ::
Did I miss something?? Camera.exe is there, but doesn't work
Brandon
My Ext ROM is not write protected, and I'm able to run applications in the EXT ROM Folder. I deleted the 2 TMD and the T-Mobile cab files, but I have not nticed a big difference, nor is my GPRS back to always on, which it should be now.
Perhaps the device requires another hard reset without these cab files in place prior to the changes taking actual effect. Does anyone know if my assumption is accurate about the required hard reset?
Ed
what dictates if the ExtROM is write protected or not? is it the version? or the hardware itself? or a mix of the version with the OS checks?
cuz i believe the ROM version is dictated by the version_AKU1.sa.cab. does that mean we can hack the cab (or use a diff version) to disable the write protection?
i'm using a himalaya btw.
I have a question or two.
I'd also like to know if it is possible to modify CAB files so they install an application and then also put in your purchased key or serial depending on the application so it's already registered to yourself. It seems like it must be possible because the GPRS Monitor on the T-Mobile Extended ROM is already Registered when you try and register it yet I was under the impression it normally has to have a key entered to turn it into the full version with no limits.
This would be great if this was possible, if it's a key file then it's simple to copy it over but how about automatic registry entries? Are these done similar to Windows .reg files? Does anyone have any info if a .reg file can be make and run from the Extended ROM to make changes to the registry? This would also allow me to key in a few other things I'd like presetup.
Is there a way to see what registry changes a CAB file makes other than from purchasing MagicCAB? Is there a free program like this? It seems like a reasonable program from the info but I don't want to spend 10 dollars on a program I might only use once or twice.
Acutally, one more while I'm here. Does anyone have a CAB installation version of CabInstl which puts a shortcut in the Programs or an easy way for me to make that? I've set it up so it will copy the EXE in manually along with a shortcut but I've yet to try it. I think it should work OK I imagine, just might be neater and have an uninstall if it's in a CAB format?
Can you delete files from the extended ROM script? Just so I can clear out a few folders of things I don't want in there when I do a hard reset?
Thanks for all your help. I'm looking forward to making a super kick ass Extended ROM for myself, I'm half way there
Updating the indirect way
Had a few problems with the updating process... and thought i would explain how I got around them!
First I updated to the standard 16007DE ROM
Then I installed the Extended Rom Viewer, and then because it is protected, i copied the contents to my HDD.
Then i tried to open the Rom update from T-mobile with the Extended ROM editor, but kept on getting file access errors The only one i could open was the NL 13006 version. So I changed the splash screen, deleted the origianl contents, and then inserted the contents from my updated original Extended ROM, as well as a few other bits that i could find, IE the extended ROM viewer. It is updating at the moment, So I hope it all works.
I have a few questions though!
Does anyone know a way in which I can automatically install a few themes, and a few ringtones? I have a few MIDI files that i want to be installed into the windows\rings folder, and the themes need to go in a folder called themes in My Documents. I also wanted to ask if there is a way to extract the CAB from another program, for instance Voice Commander. It is an MSI, but only works in windows!!!
Any help would be greatly appreciated...
Greets from Hannover, Germany
Juggs :?
Is this going to work:
- Download ER2003Edit
- Download the O2 XDA2 ROM 1.60.50
- Download the T-Mobile MDA2 ROM 1.60.36
- Remove O2 apps i don't want to use
- Add applications from T-mobile rom which i want to use
- Change ROM provider from O2 rom to to T-Mobile
- Save new O2 ROM and upgrade
But... I want to add custom ring tones to contacts, and if possible also want to add custom picture. Also my camera must be able to work. Which software do i need for this?
Because.. All i want to upgrade is today theme to O2's and also the software to 1.60.50... Does the O2 rom also has an "TMDNLCustomize.sa.CAB" ?
Greek full support language for qtek 2020
Hello,
this is a very intresting site!
Can anyone tell me is exist & where can i dinf an extended rom for qtek 2020 with full support of greek language?
Also there any newer version than the 1.66.00 wwe extended1.66.130 radio 1.10.00 wihich my qtek 2020 has??
best regards
george
A) For NOT Write Protected Extended Rom:
If your XDA2 Extended Rom is not write protected just add the new files you want, you can find on the forum many different extend rom files (O2, T_Mobile, Orange) and kitchen your own extended Rom by adding the cab files directly in the Extended_rom directory and soft reset.
B) For Write Protected Extended Rom:
The only way for the moment (until we find a way to make the rom writable) is to use the upgrade programs used by the operators and ER2003Edit program.
Click to expand...
Click to collapse
2 questions for you,
1. how do i know whether my rom is the editable 1 or the non editable one?
2. I tried option A, just mergly adding the CAB files into the EXTROM but... when the hard reset was perform it did not install the CAB files i added in? what could be the prob i know there is a "autorun.exe" in it but i dunno whether will it affect the process. I also notice a "config.txt" in the extrom, tried editing it but it seems that nothing happen
Reason for adding the cab files is because i was using a 1.72.00 rom with radio stack 1.12 but intend to change it to radio stack 1.14 and also try cooking up my own rom in the ktchen but after doin so its like nothing happen. need some advice for cooking roms in the kitchen been searching the forum... found a few but its all talking about Linux platform.
Hi Kelvin,
1)
The way to know if your rom is not writ protected is if you see a folder called extended_rom in the root of XDAII and if you can add files in it.
If not, there’s a nice tool to make the extended_rom visible and to make it writable.
http://forum.xda-developers.com/viewtopic.php?t=8422&highlight=extended+rom+hide
2) The config.txt is made to lunch the programs in the extended rom when you hard reset the XDA or when it starts for the first time.
You just need to put the cab files in your extended_rom folder and edit the config.txt this way:
Exemple:
I added the cab file vxIPConfig.ppc3_arm.CAB in the folder extended_rom
and added this line in config.txt
CAB: \Extended_ROM\vxIPConfig.ppc3_arm.CAB
Cheers,
Yann
hi yann,
i tried doing that way as i figured out that config is like a startup "prg" to actually start the programs installing when hard reset is performed. But the thing is i cannot make the programs i added in the install after the hard reset is perform. I don't know why but the rest of the cab files can be done. Do adding of all this cab files into the ROM consider cooking ROM??? not really fimilar with the terms of cooking ROM unless that is the way.
Hi
After installing the HTC TyTN 1.35 ROM on my Telstra iMate JasJam, in the phone settings program -> BAND, the GSM(900+1800)+UMTS(850) band had disappeared.
I installed the same radio version as the original one in the JasJam, but this particular band didn't come up.
So I re-installed the JasJam 1.31, and sure enough GSM(900+1800)+UMTS(850) was back in the list.
Now, interestingly I performed a hard reset, and this time prevented the installation of all the extra software that is installed after a fresh boot by pressing the reset button just when the window "Will install customization in 3s" (or something to that effect)
When I went into the phone settings -> Band, the GSM(900+1800)+UMTS(850) option had disappeared too !
So obviously it is something installed after the original boot.
Using Fit4CatTweaker , I then enabled the extended_rom and run the Autostart.exe program, and all the cab installed there were installed.
*BUT* after a reboot the GSM(900+1800)+UMTS(850) option is still not there !!
So it looks that this option isn't activated by any of the cab files located in extended_rom?
So the question is:
Is there any other programs installed after the first boot that are not located in the extended_rom drive?
When
When after the hard reset I let the JasJam install the default software, I see that it installs iMate_Smoosh.tsk software which isn't located on the extended_rom drive.
The first software to be installed by the Autostart.exe in extended_rom is Default_CAAVPPC_IMEI_2.6.83_range.CAB.
What is going on? where are the missing cab files?
Thanks
Jean-Yves
In your phones Windows directory is either a directory entitled "Preconfig" or two files called "preconfig.exe" and "preconfig.txt". If there is the directory, the two files will be in there.
You can see what is installed before the Extended ROM by looking at the contents of the preconfig.txt file. It's basically the same format as the similar file in the Extended ROM directing what is to be installed, although the preconfig.txt entries contain both XML files and CABs, something I haven't noticed from Extended ROM. It's the preconfig.exe file and the preconfig.txt file that launches AUTORUN.EXE in Extended ROM after it does the initial setup.
The most current HTC ROM's preconfig.txt file reads:
LOCK:Enabled
EXEC:\Windows\cusTSK.exe \Windows\HTC_Default.tsk (?)
EXEC:\Windows\SetHSDPA.exe /Enable (automatically enables HSDPA)
CAB: \Windows\MP_CVSDcpl_20060920.cab (adds the control panel icon for Voice Speed Dial)
XML: \Windows\PP_disconnectButtonLong.xml (adds the feature of disconnecting the data connection when you hold down the hang-up phone button for a long time)
XML: \Windows\PP_EONS.xml (?)
XML: \Windows\PP_Operator_Name.xml (?)
XML: \Windows\Brightpoint_Certificates.xml (adds Brightpoint Security Certificates)
XML: \Windows\Dangaard_Certificates.xml (same with Dangaard Certs.)
XML: \Windows\P_SMS_UnicodeEnable.sa.xml (sets SMS for Unicode ASCII)
XML: \Windows\PP_Phone_ECall.xml (?)
XML: \Windows\PP_PhoneSetting.xml (?)
Hide:Enabled
EXEC:\Extended_ROM\autorun.exe (Launches rest of post hard-reboot or ROM load setup)
LOCKisabled
RST: Reset
S
Hi
Thank you for that, I actually figured out which file was being installed.
Is there a way to edit the PreConfig.txt file? I'd like to add the XML entry that adds the other UMTS band...
I'm not sure I can the extra lines in the PreConfig.txt file in the Extended Rom
JY
Well, you can't use XML stuff in the Extended_Rom, it has no effect
This may sound stupid, but is there anyway to run the xml files after preAutorun has run preconfig.txt? I would like to do exactly like jyavenard and execute some of the xml files to setup all the connections settings as per Vodafone but do it after the 1.35 HTC ROM update.
Actually I'd like to do it once the device has fully hard booted and run preconfig.txt then I could just use the appropriate (large) xml file to drop the connections, network and dialer settings into the registry.
Sorry if I'm missing something but I have searched and searched to be able to do this.
John
First, I'd like to express how impressed and pleased I've been with DCD's kitchen work. Our v3.0.1 phone was working great but I decided to update to v3.1.2 / radio v3.39 the other day just to stay up to date. Since we prefer MS Voice Command to the Cyberon stuff, I decided to bake VC into the ROM as an OEM rather than as a CAB (just to ensure a baseline voice dialing capability in the even of a hard reset). In doing so, I discovered an issue that prevents this from working correctly without a registry tweak after the fact.
Basically, in order for MSVC to work correctly with a Bluetooth headset, a couple of registry settings need to be in place. The key one is:
HKLM\Software\Microsoft\Bluetooth\AudioGateway
BTAGExtModule =vcbthag.dll
Another one that I have been applying (although I don't know if it's required any longer in v1.6) is
HKLM\Software\OEM\VoiceCommand
Path=\Windows\VoiceCMD.exe
These keys are actually set up correctly by the OEM installation folder for Voice Command. The problem with the kitchen, however, is that the .RGU file in the OEMDrivers folder in the kitchen's OEM folder seems to be applied *after* the .RGU file in the MSVC folder, causing them to be overwritten with default values that break the use of Bluetooth headsets with Voice Command.
I've edited the OEMDrivers .RGU file to fix this, but I imagine I'll have to do so with every kitchen release going forward. I'm wondering if it makes more sense to make sure that the .RGU files from any user-added OEMs are applied after OEMDrivers so that they can override the defaults with values appropriate to the function of those added packages. Anyone else experience this?
drgreenberg said:
First, I'd like to express how impressed and pleased I've been with DCD's kitchen work. Our v3.0.1 phone was working great but I decided to update to v3.1.2 / radio v3.39 the other day just to stay up to date. Since we prefer MS Voice Command to the Cyberon stuff, I decided to bake VC into the ROM as an OEM rather than as a CAB (just to ensure a baseline voice dialing capability in the even of a hard reset). In doing so, I discovered an issue that prevents this from working correctly without a registry tweak after the fact.
Basically, in order for MSVC to work correctly with a Bluetooth headset, a couple of registry settings need to be in place. The key one is:
HKLM\Software\Microsoft\Bluetooth\AudioGateway
BTAGExtModule =vcbthag.dll
Another one that I have been applying (although I don't know if it's required any longer in v1.6) is
HKLM\Software\OEM\VoiceCommand
Path=\Windows\VoiceCMD.exe
These keys are actually set up correctly by the OEM installation folder for Voice Command. The problem with the kitchen, however, is that the .RGU file in the OEMDrivers folder in the kitchen's OEM folder seems to be applied *after* the .RGU file in the MSVC folder, causing them to be overwritten with default values that break the use of Bluetooth headsets with Voice Command.
I've edited the OEMDrivers .RGU file to fix this, but I imagine I'll have to do so with every kitchen release going forward. I'm wondering if it makes more sense to make sure that the .RGU files from any user-added OEMs are applied after OEMDrivers so that they can override the defaults with values appropriate to the function of those added packages. Anyone else experience this?
Click to expand...
Click to collapse
its because buildos is parsing your MSVC rgu before the OEMDrivers rgu (which then overwrites btagextmodule).
i fixed MSVC in the next release (it will be included) with a provxml.
dcd1182 said:
its because buildos is parsing your MSVC rgu before the OEMDrivers rgu (which then overwrites btagextmodule).
i fixed MSVC in the next release (it will be included) with a provxml.
Click to expand...
Click to collapse
I figured as much (after looking through all the RGU files to see which ones matched the condition the phone was coming up in). Thanks so much for responding to me and for actually fixing this in the next release.
Please help me!!!
I bought a brand new HTC Touch2 in December 2009 from a local shop in Greece. Originally, it had the Greek ROM preinstalled (the menus, commands e.t.c. were Greek and it had a special Greek/English Keyboard with a special Language Switching button above the Shift button).
However there were some problems. The Greek translation was awful and the phone often crashed. So, I decided to flash the English ROM. I flashed the HSPL - which I found in this forum - and then installed the original WWE ROM from HTC Pedia. Unfortunately, this ROM doesn't include a Greek Keyboard...
I tried everything (Fixes, Registry Hacks, EzInput Packages, Advanced Configuration Tool 3.3 and also tried to understand and edit the Registry keys: ezinput, ezsip, tegic). I realized that all the files needed for the Greek Keyboard existed in the Windows folder of the WWE ROM. So, what I need is the correct Configuration.
I am desperate... I don't know what to do. Can you help me please? Can you create a cab with the correct Configuration (either extracted from the Registry of a Greek ROM or cooked, maybe). Or, if that can't be done, can you upload a Greek ROM? I only need the Greek/English Keyboard (EzInput Configuration)...
Please, it is very important!
Thanks in Advance...
try ths keyboard is better:
http://forum.xda-developers.com/attachment.php?attachmentid=297994&d=1269370262:o
would this work for wm6.5 (htc touch pro2) ?
TIA
@ngelos said:
I realized that all the files needed for the Greek Keyboard existed in the Windows folder of the WWE ROM. So, what I need is the correct Configuration.
Click to expand...
Click to collapse
I had a very similar issue as you, using a WWE ASIA ROMand wanting a special Chinese input. Same situation: All files seem to be there, but no idea how to get the keyboard. What I did was install the Chinese ROM (would be the Greek one for you), hard reset, select the wanted keyboard, and dump the registry to a text file.
Next I installed the "target" ROM (WWE ASIA for me, WWE from HTCPedia for you), hard reset, and dump the registry again.
Then compare both registry text files. I searched for everything that looked like ezInput related, and finally figured out that for me I needed to change the following:
Code:
1) Delete these 3 keys:
[HKEY_CLASSES_ROOT\CLSID\{F50603D1-CF2F-41D8-A74B-651226633FF0}
[HKEY_CLASSES_ROOT\CLSID\{5AAFAF99-8D99-4466-A66D-95C44B608A84}
[HKEY_CLASSES_ROOT\CLSID\{9E06C6B8-FE4D-4206-9A5B-6E4C1B8B6AD7}
2) in [HKEY_LOCAL_MACHINE\SOFTWARE\HTC\ezsip] change the following values:
"CurrentSIP"=dword:00000da4
"HWChineseMode"=dword:00000001
3) in [HKEY_CURRENT_USER\Software\Keytouch\Multiplay] change the following values:
"nSelectedIme"=dword:00000003
"DefaultIME"="ZY"
Maybe you can do something similar. Good luck!
PS: Here are my adventures described:
http://forum.xda-developers.com/showthread.php?t=659970
Thank you very much for this keyboard!
It was just what i needed!
EZInput Greek from Touch3g forum
http://forum.xda-developers.com/attachment.php?attachmentid=305403&d=1270649275