[I asked this in the wrong forum previously -- sorry for the repeat topic]
I would like to understand where the Model No string comes from. This value is shown in device info and apparently checked by some software to determine if it's running on "known" or "supported" phones (e.g., Bing).
For example this is "T-Mobile_LEO" on a US HD2.
How does a chef influence this value, and more importantly, is it possible for me to change it without needing a new ROM image or having to reflash (e.g., via the registry, or updating a file, etc)?
Some pieces of software simply check model.txt (in the windows folder).
[HKEY_LOCAL_MACHINE\Security\Internet Explorer\User Agent]
Click to expand...
Click to collapse
is used for internet based stuff
[HKEY_LOCAL_MACHINE\Software\Microsoft\ActiveSync]
"DeviceModel"="XV6875"
Click to expand...
Click to collapse
can be used
Just do a search for the model number shown in device info in total commander (do a search in the registry section), and see what comes up.
WoZZeR999 said:
Some pieces of software simply check model.txt (in the windows folder).
is used for internet based stuff
can be used
Just do a search for the model number shown in device info in total commander (do a search in the registry section), and see what comes up.
Click to expand...
Click to collapse
User-Agent is possible, but I don't think he's referring to the others. He said "T-Mobile_LEO", but HTC won't show out code names in these places except User-Agent. Maybe the OP can specific this question?
On an HD2, Settings tab -> "About Phone" -> Phone Identity
Bing picks this up:
NOTE: the above is on a cooked ROM where the chef has gratuitously changed the Model No (on a stock ROM, it's something like T-Mobile_LEO). Unfortunately this causes Bing to think it's in beta mode because it doesn't recognize the phone it's running on. I want to know if I can change it back without reflashing.
Thanks for the tips, folks. Both registry settings mentioned above have "T-Mobile_LEO" in them.
However \windows\ModelName.txt contains the value the chef changed it to ("HTC HD2").
Is it possible for me to change ModelName.txt even though it's a ROM file?
Secondarily I'm also curious about how the registry values got initialized to T-Mobile_LEO -- where specifically did *that* string come from, given that ModelName.txt contains a different string?
I created a cab with the WM6.1 SDK and it worked. My phone identifies as a T-Mobile_LEO and Bing (after being uninstalled and reinstalled) stops identifying itself as beta.
Thanks for the tips folks.
Ok happy ending lets change the name as OP didnt do it
tai4de2 said:
Thanks for the tips, folks. Both registry settings mentioned above have "T-Mobile_LEO" in them.
However \windows\ModelName.txt contains the value the chef changed it to ("HTC HD2").
Is it possible for me to change ModelName.txt even though it's a ROM file?
Secondarily I'm also curious about how the registry values got initialized to T-Mobile_LEO -- where specifically did *that* string come from, given that ModelName.txt contains a different string?
Click to expand...
Click to collapse
Yes, you can. Copy it out and edit it, then use 3rd-party file explorers such as Resco or Total Commander to overwrite the ROM file. The identity string is also a registry:
Code:
[HKEY_LOCAL_MACHINE\Ident]
"Name"="T-Mobile_LEO"
+ Que PPC said:
Ok happy ending lets change the name as OP didnt do it
Click to expand...
Click to collapse
May I know for my knowledge what does this [OP] indicate?
I have searched my kitchen endlessly for the T-Mobile_LEO string that shows up as per picture one in the earlier post, and cannot find it. The ModelName.txt file contains the correct text (as I have a Touch Pro 2).
The reg key that seems to set this is HKLM\system\platform\OEMString but I cannot find the source of this in the kitchen.
Any help would be greatly appreciated.
c_shekhar said:
May I know for my knowledge what does this [OP] indicate?
Click to expand...
Click to collapse
Original Poster
NRGZ28 said:
Original Poster
Click to expand...
Click to collapse
Thanks.......
crazyC said:
I have searched my kitchen endlessly for the T-Mobile_LEO string that shows up as per picture one in the earlier post, and cannot find it. The ModelName.txt file contains the correct text (as I have a Touch Pro 2).
The reg key that seems to set this is HKLM\system\platform\OEMString but I cannot find the source of this in the kitchen.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Does anyone have any further sugegstions? I am at a loss with this as to where this is being set. My best guess is Manila and that is why the search is not picking it up? I am no good with manila so am seeking guidance.
Cheers
It depends which kitchen or tools you are using.
In Oskitchen you can find it in 'NBH Structure.xml'
It contains the rom version and settings to create the nbh.
The kitchen uses nbImageTool.exe made by Da_G which reads this file to create the nbh.
crazyC said:
Does anyone have any further sugegstions? I am at a loss with this as to where this is being set. My best guess is Manila and that is why the search is not picking it up? I am no good with manila so am seeking guidance.
Cheers
Click to expand...
Click to collapse
Thank you for the reply.
The nbh structure.xml correctly identifies my device as a RHOD 300. The T-Mobile_LEO must be coming from somewhere else.
I use OsKItchen and the source dumped rom was from a Rhodium and so my OEM and device profile comes from that. The erroneous model no must be coming from an EXT package as far as I can see.
If you are looking for a package I would say Oemversion.
crazyC said:
Thank you for the reply.
The nbh structure.xml correctly identifies my device as a RHOD 300. The T-Mobile_LEO must be coming from somewhere else.
I use OsKItchen and the source dumped rom was from a Rhodium and so my OEM and device profile comes from that. The erroneous model no must be coming from an EXT package as far as I can see.
Click to expand...
Click to collapse
crazyC said:
Thank you for the reply.
The nbh structure.xml correctly identifies my device as a RHOD 300. The T-Mobile_LEO must be coming from somewhere else.
I use OsKItchen and the source dumped rom was from a Rhodium and so my OEM and device profile comes from that. The erroneous model no must be coming from an EXT package as far as I can see.
Click to expand...
Click to collapse
If you have swype, it would probably be coming from there.
Aaaahhhhh - now that would explain why I cannot find any reference to it in my kitchen. I could never get swype to work as an EXT package the way I wanted so it installs within XDA-UC.
Time to pull that cab apart I think.
crazyC said:
Aaaahhhhh - now that would explain why I cannot find any reference to it in my kitchen. I could never get swype to work as an EXT package the way I wanted so it installs within XDA-UC.
Time to pull that cab apart I think.
Click to expand...
Click to collapse
If you do change the Model name, Swype probably won't work. It looks at the model name.
rgb-rgb said:
If you do change the Model name, Swype probably won't work. It looks at the model name.
Click to expand...
Click to collapse
Yes - just worked that out the long way.
Oh well, at least I know how and why its there now.
Thanks all for the help.
Related
Am using the Dopot CT9000 with the English ROM and there is this program called Quickmark which I think is a name card scanning software. The thing is, all the instructions in the program are in boxes and not in English. Is there any way around this?
Does TyTN have this program?
Tell me pls the following:
1. Which language -exactly- have you installed on your device?
2. What filenames have the two files Quickmark.xxxx.dll (whereas xxxx stands for the landcode as defined by Microsoft).
Check this and post it here. Then there will be a solution for you.
The QR Codes are really cool!
ghl10000 said:
Tell me pls the following:
1. Which language -exactly- have you installed on your device?
2. What filenames have the two files Quickmark.xxxx.dll (whereas xxxx stands for the landcode as defined by Microsoft).
Check this and post it here. Then there will be a solution for you.
The QR Codes are really cool!
Click to expand...
Click to collapse
Thank you so much for your help.
1. I presume the language is english as everything else in my CT9000 is in English and all. The keyboard has some chinese strokes but that's the only thing chinese about it. My software version are as follows:
ROM: 1.23.707.1
ROM date: 06/28/06
Radio: 1.06.00.10
Protocol: 32.37.7010.01H
Is there any other information you need to know?
2. The 2 files you were talking about are as follows:
Quickmark.0409.dll
Quickmark.0804.dll
Would appreciate any help I can get on this.
Thank you.
vapor said:
2. The 2 files you were talking about are as follows:
Quickmark.0409.dll
Quickmark.0804.dll
Click to expand...
Click to collapse
Delete QuickMark.0809.dll and rename QuickMark.0409.dll to QuickMark.0809.dll, that's it.
pof said:
vapor said:
2. The 2 files you were talking about are as follows:
Quickmark.0409.dll
Quickmark.0804.dll
Click to expand...
Click to collapse
Delete QuickMark.0809.dll and rename QuickMark.0409.dll to QuickMark.0809.dll, that's it.
Click to expand...
Click to collapse
did you mean delete the quickmark.0804.dll file and rename the quickmark.0409.dll to quickmark.0809.dll?
if you did, i have done it and there is no change. even a soft reset does not seem to work.
vapor said:
pof said:
Delete QuickMark.0809.dll and rename QuickMark.0409.dll to QuickMark.0809.dll, that's it.
Click to expand...
Click to collapse
did you mean delete the quickmark.0804.dll file and rename the quickmark.0409.dll to quickmark.0809.dll?
Click to expand...
Click to collapse
QuickMark.0409.dll contains the english text.
QuickMark.0809.dll contains the chinese text.
So, delete QuickMark.0809.dll and either rename or copy QuickMark.0409.dll to QuickMark.0809.dll, so the program will always find the dll with the english text.
pof said:
vapor said:
pof said:
Delete QuickMark.0809.dll and rename QuickMark.0409.dll to QuickMark.0809.dll, that's it.
Click to expand...
Click to collapse
did you mean delete the quickmark.0804.dll file and rename the quickmark.0409.dll to quickmark.0809.dll?
Click to expand...
Click to collapse
QuickMark.0409.dll contains the english text.
QuickMark.0809.dll contains the chinese text.
So, delete QuickMark.0809.dll and either rename or copy QuickMark.0409.dll to QuickMark.0809.dll, so the program will always find the dll with the english text.
Click to expand...
Click to collapse
but i do not have an 0809, only a 0804.
vapor said:
pof said:
QuickMark.0409.dll contains the english text.
QuickMark.0809.dll contains the chinese text.
Click to expand...
Click to collapse
but i do not have an 0809, only a 0804.
Click to expand...
Click to collapse
OK, delete QuickMark.0804.dll and copy or rename QuickMark.0409.dll to QuickMark.0804.dll.
The point is that the program finds the english dll...
pof said:
vapor said:
pof said:
QuickMark.0409.dll contains the english text.
QuickMark.0809.dll contains the chinese text.
Click to expand...
Click to collapse
but i do not have an 0809, only a 0804.
Click to expand...
Click to collapse
OK, delete QuickMark.0804.dll and copy or rename QuickMark.0409.dll to QuickMark.0804.dll.
The point is that the program finds the english dll...
Click to expand...
Click to collapse
somehow its still not working. it still shows boxes. have done a soft reset. is there any other way?
anyone else can help me out here?
has anyone else faced this problem and can help? maybe upload the right file?
All CAB'd up and ready to go.
P
http://www.modaco.com/index.php?showtopic=244416#
modaco said:
All CAB'd up and ready to go.
P
http://www.modaco.com/index.php?showtopic=244416#
Click to expand...
Click to collapse
thanks for the file modaco.
i tried to install over the current installation and it doesnt work
i removed the original and installed this one and it doesnt work
i tried renaming the file in the new installation and it also doesnt work
by sayin it doenst work means it still shows the boxes.
any idea?
Hello,
well Chinese isn’t Chines as is with German and German (or English and English) in the sense of localization as defined by Microsoft !
Just have a look at this most valuable “List of Locale IDs” published by Microsoft:
http://www.microsoft.com/globaldev/reference/winxp/xp-lcid.mspx
I had the same problem as you when I first started Quickmark and was even puzzled for a moment when I had restarted it again, having changed the locale ID to German.
All menue items kept showing up as little boxes – which is what one usually sees when there is a problem with the localization.
Resolution was that there is a special modified Locale ID for Austria !
(Here in Austria German is the official language, but there is a Local ID for German (Austria), which is 0c07 and for German (Standard = Germany), which is 0407.)
When I changed the English language file to Quickmark.0c07.dll (instead of the previously tried Quickmark.0407.dll) the English menue showed up again !
As you mentioned that on your keyboard you can see some Chinese keys I’d suppose your device isn’t a US-English version.
Also I’d assume from the flag you are using next to your nick that your native tongue isn’t English either, correct ?
What you should do:
Go to Settings | Language (or Localization or whatever it be called on your device) and check, which language you have set there.
Then look up the Locale ID for this language setting in the table (see link above).
Replace the Locale ID in the filename of the English language dll.
Reboot !!!
Now you should see the English menue instead of the boxes.
I don’t know anyone where this procedure hasn’t resolved this problem !
ghl10000 said:
Hello,
well Chinese isn’t Chines as is with German and German (or English and English) in the sense of localization as defined by Microsoft !
Just have a look at this most valuable “List of Locale IDs” published by Microsoft:
http://www.microsoft.com/globaldev/reference/winxp/xp-lcid.mspx
I had the same problem as you when I first started Quickmark and was even puzzled for a moment when I had restarted it again, having changed the locale ID to German.
All menue items kept showing up as little boxes – which is what one usually sees when there is a problem with the localization.
Resolution was that there is a special modified Locale ID for Austria !
(Here in Austria German is the official language, but there is a Local ID for German (Austria), which is 0c07 and for German (Standard = Germany), which is 0407.)
When I changed the English language file to Quickmark.0c07.dll (instead of the previously tried Quickmark.0407.dll) the English menue showed up again !
As you mentioned that on your keyboard you can see some Chinese keys I’d suppose your device isn’t a US-English version.
Also I’d assume from the flag you are using next to your nick that your native tongue isn’t English either, correct ?
What you should do:
Go to Settings | Language (or Localization or whatever it be called on your device) and check, which language you have set there.
Then look up the Locale ID for this language setting in the table (see link above).
Replace the Locale ID in the filename of the English language dll.
Reboot !!!
Now you should see the English menue instead of the boxes.
I don’t know anyone where this procedure hasn’t resolved this problem !
Click to expand...
Click to collapse
thank you so much for your input. I will go and try it out.
However I do not understand the Settings > Language part. Where can I find it? Under Regional Settings? Or somewhere else? I hope you can guide me on this as I could not find it.
just tried it out and it works great now wooohooo. thank you all for helping me out.
vapor said:
just tried it out and it works great now wooohooo. thank you all for helping me out.
Click to expand...
Click to collapse
Yeaaaah !!!
The QR Codes are a really cool application.
Actually in my opinion the coolest "fun" application I can think of.
(I am no gamer, so those games do not really phascinate me.)
However on a MS Smartphone (I have the Qtek 8300) and Nokia phones (tried it out on my 6680, whose camera is quite good) this application even works better:
You just have to point your phone onto a QR Code (can even be done rather fast and unprecise) and the action is triggered automatically - WITHOUT having to press a button, as on the TyTN !!!!!
This is a BIG advantage, because when pressing a button you move the device a tiny little bit.
And as the camera resolution of these phone devices aren't too high, this might be enough for not being able to decode the QR.
Actually I have no idea why Quickmark has decided to add this "Press a Button" requirement on the TyTN.
(Maybe they just ported the code and the automatic trigger mechanism is different on the Hermes platform.)
Anyway Quickmark should optimize this for the TyTN !!!!!
What do you think ? (Question to the audience.)
vapor said:
just tried it out and it works great now wooohooo. thank you all for helping me out.
Click to expand...
Click to collapse
Yeaaaah !!!
The QR Codes are a really cool application.
Actually in my opinion the coolest "fun" application I can think of.
(I am no gamer, so those games do not really phascinate me.)
However on a MS Smartphone (I have the Qtek 8300) and Nokia phones (tried it out on my 6680, whose camera is quite good) this application even works better:
You just have to point your phone onto a QR Code (can even be done rather fast and unprecise) and the action is triggered automatically - WITHOUT having to press a button, as on the TyTN !!!!!
This is a BIG advantage, because when pressing a button you move the device a tiny little bit.
And as the camera resolution of these phone devices aren't too high, this might be enough for not being able to decode the QR.
Actually I have no idea why Quickmark has decided to add this "Press a Button" requirement on the TyTN.
(Maybe they just ported the code and the automatic trigger mechanism is different on the Hermes platform.)
Anyway Quickmark should optimize this for the TyTN !!!!!
What do you think ? (Question to the audience.)
ghl10000 said:
Yeaaaah !!!
However on a MS Smartphone (I have the Qtek 8300) and Nokia phones (tried it out on my 6680, whose camera is quite good) this application even works better:
Click to expand...
Click to collapse
Which version of QuickMark did you use for Qtek 8300?
if i want to keep a certain rom but change its (as in trinity from 20273 to 22222) then how to do it.
Simple, you don't!
You have to port the ROM over. If you're refering to just changing the ROM number without actually changing the ROM itself, why would you do that? (Well, to be fair, my LZX ROMs report the wrong number, so this might be something I'd be interested in knowing, too.
ivanmmj said:
You have to port the ROM over. If you're refering to just changing the ROM number without actually changing the ROM itself, why would you do that? (Well, to be fair, my LZX ROMs report the wrong number, so this might be something I'd be interested in knowing, too.
Click to expand...
Click to collapse
of course not, Why would i just change the number??
I mean when rom cookers release new roms with new build, then the whole rom is extracted from another phone (e.g. samsung omnia)??. so what are the base files that represent this built ?? those files which i will then add new programs upon to cook my rom??
In other words "WHAT IS THE BUILT?? WHICH FILES??"
thanks for your help
aalim said:
of course not, Why would i just change the number??
I mean when rom cookers release new roms with new build, then the whole rom is extracted from another phone (e.g. samsung omnia)??. so what are the base files that represent this built ?? those files which i will then add new programs upon to cook my rom??
In other words "WHAT IS THE BUILT?? WHICH FILES??"
thanks for your help
Click to expand...
Click to collapse
The 22222 build isn't real. As far as porting, you grab the sys folder and the part of the XIP corresponding to WM without the device specific items. It really depends on the phone you have.
this is what i use and it works all the time:
http://forum.xda-developers.com/showpost.php?p=2051339&postcount=2
oh, and build 22222 is not real, as aforementioned. someone just hex edited the numbers
mbarvian said:
this is what i use and it works all the time:
http://forum.xda-developers.com/showpost.php?p=2051339&postcount=2
oh, and build 22222 is not real, as aforementioned. someone just hex edited the numbers
Click to expand...
Click to collapse
That's exactly what i needed
Have Trinity, hope it works for it smoothly
thanks mbarvian
thanks everybody
Hi, This link which wrote few post ago is dead. Can some explain here how to change build of windows mobile in rom?
Hi all,
This post is about getting the orginal WWE Asia HTC HD2's font into Artermis ROM.
1) Install the attached cab
2) Soft reset
Note 1: I only tested in fresh ROM environment, which is V10,V11
Note 2: These files are taken from RUU_Leo_hTC_Asia_WWE_1.66.707.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship.exe
One step closer to stock ROM "Philosophy"
ksk622 said:
Hi all,
This post is about getting the orginal WWE Asia HTC HD2's font into Artermis ROM.
I have tried various cabs before like ricky, RobRedbeard- LIA, sunglobe etc... and i have no idea what are the cabs actually doing. some of them even replaced the original wince.nls, create some junk reg keys, make chinese font in some app overlapping...
Here is the safer technique to get chinese font support without messing around with the system files and registry.
1) Download the attached zip file and extract to your storage card
2) Copy UCSH00B-gray.ttf to \windows
3) Import this registry file, SystemLink.reg
4) Soft reset
Note 1: I only tested in fresh ROM environment, which is V10
Note 2: These files are taken from RUU_Leo_hTC_Asia_WWE_1.66.707.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship.exe
One step closer to stock ROM "Philosophy"
Click to expand...
Click to collapse
great work on the chinese font!
is there any way of getting the ezInput keyboard from 1.66 asia ROM to work on other custom ROMs as well? thanks
alexnvidia said:
great work on the chinese font!
is there any way of getting the ezInput keyboard from 1.66 asia ROM to work on other custom ROMs as well? thanks
Click to expand...
Click to collapse
I am looking into this as well. will try my luck with the new version of "touch input".
ksk622 said:
I am looking into this as well. will try my luck with the new version of "touch input".
Click to expand...
Click to collapse
looking forward to your findings mate. cheers
temporary solution
I just tested with artermis v10 with the following
http://forum.xda-developers.com/showthread.php?p=6295918#post6295918
steps
1) download the attachment then extract all the files to a temp folder on your desktop
2) go files folder, copy & paste EzInputSettings.exe.0804.mui then rename the new file to EzInputSettings.exe.0409.mui
3) copy all the dll files from those folder name end with .ddl to parent folder (../files). you can skip HTCSipSrvc.dll
4) now go to your device, change SIP to other. change home to titanium
5) go to /windows folder and rename those dll file with same name you modified on your desktop temp folder to xxxx.dll.old( total is 11 files)
6) copy the temp folder on your desktop to your HD2
7) use total commander to move all the files inside files folder to /windows, replace all the dll & files (must make sure no overwrite error)
8) import app.reg
9) soft reset
Finally stock rom chinese support in WWE rom
Now just waiting for a kind soul to help to convert this into cab
UPDATE: Only pinyin and stroke is working...
ABOVE SOLUTION IS UNSUPPORTED NOW
I was reading somewhere that wince.nls needs to be updated to support chinese input???
Leechoonhwee said:
I was reading somewhere that wince.nls needs to be updated to support chinese input???
Click to expand...
Click to collapse
Artermis ROM is using the global version of wince.nls, thats why make this possible. Eg: we can see the 5 chinese legions in setting....
+1
Great work =D
Is it possible to make something similar using the 1.72 HKCSL_WWE stock ROM for traditional Chinese character display and input?
Thanks!
i am also very interest in this ,anyone can help to have a CAB?
yes please
+1
this would be a big help to a lot of users!
including me
global wince.nls
ksk622 said:
Artermis ROM is using the global version of wince.nls, thats why make this possible. Eg: we can see the 5 chinese legions in setting....
Click to expand...
Click to collapse
can you please upload a copy of the global wince.nls for those of us who arent on the artemis rom?
thanks
HPD
hyperpsychodreamer said:
can you please upload a copy of the global wince.nls for those of us who arent on the artemis rom?
thanks
HPD
Click to expand...
Click to collapse
Here it is...
ksk622 said:
Here it is...
Click to expand...
Click to collapse
i replaced the wince.nls, but nothing happened. i still dont get the 5 chinese regions in regional settings. also, can you check if your first post method works for google maps 4.1? in google maps, under settings, speech language, there is an option for mandarin. all i get are square boxes.. it should write chinese language, in mandarin of course. any fix for this?
alexnvidia said:
i replaced the wince.nls, but nothing happened. i still dont get the 5 chinese regions in regional settings. also, can you check if your first post method works for google maps 4.1? in google maps, under settings, speech language, there is an option for mandarin. all i get are square boxes.. it should write chinese language, in mandarin of course. any fix for this?
Click to expand...
Click to collapse
Maybe try the following:
- rename the existing wince.nls to wince.nls.old then copy the new one.
- inside your registry... remove this key [HKEY_LOCAL_MACHINE\Software\Microsoft\FontLink\SystemLink] then import the reg file from 1st post, if everything ok, only 5 entries will be recreated as following
"HelveticaNeue LT 35 Thin"="\\windows\\UCSH00B-gray.ttf,AR CrystalHeiU20 Bold(gray);\\windows\\tahoma.ttf,Tahoma"
"Helvetica Neue OTS"="\\windows\\UCSH00B-gray.ttf,AR CrystalHeiU20 Bold(gray);\\windows\\tahoma.ttf,Tahoma"
"Courier New"="\\windows\\UCSH00B-gray.ttf,AR CrystalHeiU20 Bold(gray)"
"Tahoma"="\\windows\\UCSH00B-gray.ttf,AR CrystalHeiU20 Bold(gray)"
"AR CrystalHeiU20 Bold(gray)"="\\windows\\tahoma.ttf,Tahoma"
remember to soft reset ... then enjoy the new font
alexnvidia said:
i replaced the wince.nls, but nothing happened. i still dont get the 5 chinese regions in regional settings. also, can you check if your first post method works for google maps 4.1? in google maps, under settings, speech language, there is an option for mandarin. all i get are square boxes.. it should write chinese language, in mandarin of course. any fix for this?
Click to expand...
Click to collapse
replacing the wince.nls directly doesn't work. You need to use it with reloadnls.exe which will have to be in the startup folder. do a search for it and you will find your answers. I used to write a thread for this as well, so you can try to search for it.
GiantMuffinMan said:
Great work =D
Is it possible to make something similar using the 1.72 HKCSL_WWE stock ROM for traditional Chinese character display and input?
Thanks!
Click to expand...
Click to collapse
that would be easy, if you guys really want it, I mean the traditional Chinese display and supports,
I may make 2 cabs tonight
cab 1: CHT display (mingliu.ttc, pretty fonts) and input (from Samsung HK keyboard),
cab 2: same as the above but added wince.nls with Chinese regions.
please pm to me to show your request in order to let me work on it ( I am currently using the second method )
wow~~thanks!!
it really helps~~
great work great work!!!
dioxda2 said:
that would be easy, if you guys really want it, I mean the traditional Chinese display and supports,
I may make 2 cabs tonight
cab 1: CHT display (mingliu.ttc, pretty fonts) and input (from Samsung HK keyboard),
cab 2: same as the above but added wince.nls with Chinese regions.
please pm to me to show your request in order to let me work on it ( I am currently using the second method )
Click to expand...
Click to collapse
THat would be greeaaat....
Hi Dioxda2,
i ever try your 2 roms.
those are only to display chinese right? not enter chinese right?
thanks in advance for clarifying
jack
Hi
I need hand writing for Chinese input，Can you dump your chinese version ROM and share with us?
Thank you
I have flashed the Energy ROM and love everything about it. However, once I started using it, I realized that I can't find the standard Voice Command feature anywhere on the device. Can someone please either post the cab for this file or let me know where it may have moved?
Here is what I can tell you:
- Button settings don't include the PTT button (the one I want to use)
- Voice Command isn't listed under Windows\Programs or anywhere else
- Using Manila 2.5.20151725.1
- Using Energy ROM Rhodium 23569 Sense 2.5
TragicPhill said:
I have flashed the Energy ROM and love everything about it. However, once I started using it, I realized that I can't find the standard Voice Command feature anywhere on the device. Can someone please either post the cab for this file or let me know where it may have moved?
Here is what I can tell you:
- Button settings don't include the PTT button (the one I want to use)
- Voice Command isn't listed under Windows\Programs or anywhere else
- Using Manila 2.5.20151725.1
- Using Energy ROM Rhodium 23569 Sense 2.5
Click to expand...
Click to collapse
The NRG thread has the cabs posted in the "paperclips" next to the title.
stevedebi said:
The NRG thread has the cabs posted in the "paperclips" next to the title.
Click to expand...
Click to collapse
Thanks a ton, got it working and everything. These forums are a lifesaver.
Originally Posted by stevedebi
"The NRG thread has the cabs posted in the "paperclips" next to the title."
I also have the same issue, and I just need to know which NRG thread are you referring to. I cannot find the cab file anywhere.
need help....Thanks.
JSBirdmann said:
I also have the same issue, and I just need to know which NRG thread are you referring to. I cannot find the cab file anywhere.
need help....Thanks.
Click to expand...
Click to collapse
Use the one I've attached.
I also need it.Thanks alot!
Is this for GSM only? I used it on CDMA (Verizon) and can't find any trace of it after installation. Also, the original (lower rev) installation is gone (of course)....
Off to find the original cab for Verizon WM6.5....
Tybalt39 said:
Is this for GSM only? I used it on CDMA (Verizon) and can't find any trace of it after installation. Also, the original (lower rev) installation is gone (of course)....
Off to find the original cab for Verizon WM6.5....
Click to expand...
Click to collapse
It will show up in Start > Settings > Personal > Voice Command.
cajunflavoredbob said:
It will show up in Start > Settings > Personal > Voice Command.
Click to expand...
Click to collapse
Thanks for your feedback, but that is where the original icon was located. Now no icon exists for Voice Command in the Personal file (or the System file). That's what I meant by "can't find any trace of it after installation".
[EDIT] When I decided to uninstall it, I did find it listed as uninstallable. Back on 1.6.21840 for now. Everything is working again.
Anyone know what changed in 1.6.23562?
Thank you.
Its not the good voice command y have on my (old) Touch Cruise Winmobile 6.1, try now to flash to winmobile 6.1 because i cant find many things that y have on my old phoon.
When its not works a try to sell this phoon, y dont like it at al now, only internet + keyboard and the look is better but the other things what y see makes that y want to go back to my old phone now, Android testet and seems to be better but not all works there (special no provider connection found so no callings) so the only thing y want is use my Parrot handsfree and better internet and a FM Radio, but this is not the good machine for it y think.
Spend 100 euro for nothing (simlock free) no abbo (old boxed but not selled, 1 week ago New from shop)
Sorry for my bad typing here, ym a Dutch man with no Eng. learning on school.
thanks
thank u good work
Greetings!
First off, I have little idea what I'm doing, this is my first attempt to create a custom ROM. I've searched around and can't seem to find a solution.
I've got an Xperia X1 and am using osKitchen.
The ultimate goal is to have a Japanese ROM with WM build 25369 with no additional UIs, i never use sense or whatever anyway, just the old today screen with cal, messaging, and time/date items.
I have:
Latest stock ROM for X1 (GENERIC_NAM_R3AA011)
23569_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409 (Just Eng)
initflashfiles-dat-all-langs-updated-feb-24-2010.zip
RUU_Diamond_eMobile_JPN_1.81.881.2_Radio_Signed_Diamond_52.48.25.26_1.09.25.07_Ship.exe (6.1 JPN ROM)
Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65.zip
WM6550-23563-Rollup-All-Pkgs.rar (This has all languages)
Here's what I'm doing, anyone of them (or all) could be very wrong, hopefully I've done at least one thing right:
Imported X1 ROM for OEMDrivers, OEMApps, OEMOperators, oemversion, oem_dpi
Imported 6.1 JPN ROM for OEM Lang 411
-What i did here is i copied everything over from the JPN rom's oem 411 folder into the X1 OEM Lang folder, overwrote any conflicts, deleted any 0409 muis, and copied over the file from initflashfiles zip for 0411.
Replaced OEMXipKernel with the one from Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65.zip and selected custom XIP when making the rom with the one also found in that zip. Put the rest of the files (os.nb.payload, xip.bin, uldr.nb0, romhdr.bin) into the ROM Parts folder.
Then, I Used OS, OSFiles, MSXIPKernel, MSXIPKernelLTK from the 23569_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409 zip, and the rest of the packages i used from the WM6550-23563-Rollup-All-Pkgs rar (because it had 0411 files).
I deleted dpi and lang folders that my device doesn't use (it uses 192dpi 480x800 and 0411) and built the ROM, flashed, and it shows the Sony Ericsson splash screen, and then goes black forever.
I know I must be doing something very wrong, any hints as to what?
Thanks
Pfff, what a big list,
Okay I did it this way, and I make my rom in 12 languages and they are all working.
1. Install oskitchen and import xperia rom
2. After finishing import 23563 build
3. Install another oskitchen and import diamond jpn rom
4. Copy the oem_lang 0411 and the ext packages to your kovsky kitchen be aware you put them in the right place.
5. Open the kovsky kitchen and select the Japanese language and select the packages you wanna use in your rom and you're done.
Regards,
Cool thanks!
That would be for 23563 though right? What if i wanted to use 23569 with 23563 packages? ....No real reason, higher number, figure it's better somehow....that even possible?
nemasu said:
Cool thanks!
That would be for 23563 though right? What if i wanted to use 23569 with 23563 packages? ....No real reason, higher number, figure it's better somehow....that even possible?
Click to expand...
Click to collapse
Just start with 23563, it's a good package and if you have a working rom you can alway's make the change.
Greetz,
Rataplan said:
Just start with 23563, it's a good package and if you have a working rom you can alway's make the change.
Greetz,
Click to expand...
Click to collapse
Ok sounds good, I was just thinking I probably shoulda tried with something a bit easier haha.....how would i make the change? is my approach correct?
nemasu said:
Ok sounds good, I was just thinking I probably shoulda tried with something a bit easier haha.....how would i make the change? is my approach correct?
Click to expand...
Click to collapse
If you extract the 23569 build, you only have to change the All and Common folder, but in your first post you where talking about a 25369 build and I didn't know what kind off build that was.
Succes buddy,
Make sure you have the proper wince.nls in your build. If you leave it out, the rom won't boot.
Farmer Ted said:
Make sure you have the proper wince.nls in your build. If you leave it out, the rom won't boot.
Click to expand...
Click to collapse
I used the one that came with the Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65 zip.
nemasu said:
I used the one that came with the Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65 zip.
Click to expand...
Click to collapse
I don't think there is any difference between those 2 wince.nls but if you wanna be sure just use the one in the 23563/COMMON folder.
Rataplan said:
I don't think there is any difference between those 2 wince.nls but if you wanna be sure just use the one in the 23563/COMMON folder.
Click to expand...
Click to collapse
Hmm, I've got a wince.nls in:
Sources\Devices\HTC Kovsky\Profiles\default\OEMXipKernel
Sources\Windows Mobile Builds\23569\0411\WinCENLS_Lang_0411
and
Sources\Windows Mobile Builds\23569\Common\WinCENLS_WWE
they are all different sizes....should they all be the same? or only have one? or?
nemasu said:
Hmm, I've got a wince.nls in:
Sources\Devices\HTC Kovsky\Profiles\default\OEMXipKernel
Sources\Windows Mobile Builds\23569\0411\WinCENLS_Lang_0411
and
Sources\Windows Mobile Builds\23569\Common\WinCENLS_WWE
they are all different sizes....should they all be the same? or only have one? or?
Click to expand...
Click to collapse
No I have them also, never take a look at it, only checked the file when I cooked my rom's never changed anything or replaced it with another version or from another build.