Database Info

[Q] Application Security Policy Settings "Defined" - Non-Touchscreen Windows Mobile Other

Windows Mobile powered devices are shipped with default security settings.
The security model enables Mobile Operators to make post-production changes to security settings.
This can place significant restrictions on software which has not been signed and approved.
However you can change the default settings.
Take control of applications on your phone.
"All listed settings are decimal"
1. Connect the phone through ActiveSync.
2. Run your favorite remote registry editor "CeRegEditor (Download)" "Mobile Registry Editor (Download)" on your PC.
3. Navigate to HKEY_LOCAL_MACHINE\Security\Policies\Policies
RAPI Policy:
This setting restricts the access of remote applications that are using Remote API (RAPI) to implement ActiveSync operations
HKEY_LOCAL_MACHINE\Security\Policies\Policies
DWord = 00001001 Data = Use the following-->
0 = Indicates that the ActiveSync service is shut down. RAPI calls are rejected.
1 = Indicates full access to ActiveSync is provided. RAPI calls are allowed to process without restrictions.
2 = Indicates that access to ActiveSync is restricted to the SECROLE_USER_AUTH (User Authenticated) role. RAPI calls are checked against this role mask before they are granted.
Unsigned cabs role:
If this policy is set to 0, then unsigned CABs won't install. The typical role is UserAuth which means the CABs will install but they have a similar set of privileges as code running at the Normal level. If this policy is set to Manager, then the unsigned CABs have all privileges.
None: Is equivalent to having none of the role mask bits set, and means that no unsigned .cab files can be installed.
OEM: Equipment manufacturer role.
Operator: Settings can be changed by the mobile operator.
Operator-TPS: Settings can be changed by a Wireless Application Protocol (WAP) Trusted Provisioning Server (TPS).
Manager: Provides permissions to change all of the settings on the device.
UserAuth: Settings can be changed by an authenticated user.
UserUnAuth: Settings can be changed by anyone.
A specified role mask indicates accepted unsigned .cab files are installed with the role mask specified.
HKEY_LOCAL_MACHINE\Security\Policies\Policies
DWord = 00001005 Data = Use the following-->
0 = None
2 = OEM
4 = Operator
6 = OEM, Operator
8 = Manager
10 = OEM, Manager
12 = Operator, Manager
14 = OEM, Operator, Manager
16 = UserAuth
18 = OEM, UserAuth
20 = Operator, UserAuth
22 = OEM, Operator, UserAuth
24 = Manager, UserAuth
26 = OEM, Manager, UserAuth
28 = Operator, Manager, UserAuth
30 = OEM, Operator, Manager, UserAuth
64 = UserUnAuth
66 = OEM, UserUnAuth
68 = Operator, UserUnAuth
70 = OEM, Operator, UserUnAuth
72 = Manager, UserUnAuth
74 = OEM, Manager, UserUnAuth
76 = Operator, Manager, UserUnAuth
78 = OEM, Operator, Manager, UserUnAuth
80 = UserAuth, UserUnAuth
82 = OEM, UserAuth, UserUnAuth
84 = Operator, UserAuth, UserUnAuth
86 = OEM, Operator, UserAuth, UserUnAuth
88 = Manager, UserAuth, UserUnAuth
90 = OEM, Manager, UserAuth, UserUnAuth
92 = Operator, Manager, UserAuth, UserUnAuth
94 = OEM, Operator, Manager, UserAuth, UserUnAuth
128 = Operator-TPS
130 = OEM, Operator-TPS
132 = Operator, Operator-TPS
134 = OEM, Operator, Operator-TPS
136 = Manager, Operator-TPS
138 = OEM, Manager, Operator-TPS
140 = Operator, Manager, Operator-TPS
142 = OEM, Operator, Manager, Operator-TPS
144 = UserAuth, Operator-TPS
146 = OEM, UserAuth, Operator-TPS
148 = Operator, UserAuth, Operator-TPS
150 = OEM, Operator, UserAuth, Operator-TPS
152 = Manager, UserAuth, Operator-TPS
154 = OEM, Manager, UserAuth, Operator-TPS
156 = Operator, Manager, UserAuth, Operator-TPS
158 = OEM, Operator, Manager, UserAuth, Operator-TPS
192 = UserUnAuth, Operator-TPS
194 = OEM, UserUnAuth, Operator-TPS
196 = Operator, UserUnAuth, Operator-TPS
198 = OEM, Operator, UserUnAuth, Operator-TPS
200 = Manager, UserUnAuth, Operator-TPS
202 = OEM, Manager, UserUnAuth, Operator-TPS
204 = Operator, Manager, UserUnAuth, Operator-TPS
206 = OEM, Operator, Manager, UserUnAuth, Operator-TPS
208 = UserAuth, UserUnAuth, Operator-TPS
210 = OEM, UserAuth, UserUnAuth, Operator-TPS
212 = Operator, UserAuth, UserUnAuth, Operator-TPS
214 = OEM, Operator, UserAuth, UserUnAuth, Operator-TPS
216 = Manager, UserAuth, UserUnAuth, Operator-TPS
218 = OEM, Manager, UserAuth, UserUnAuth, Operator-TPS
220 = Operator, Manager, UserAuth, UserUnAuth, Operator-TPS
222 = OEM, Operator, Manager, UserAuth, UserUnAuth, Operator-TPS
Unsigned Applications Policy:
This setting indicates whether unsigned applications are allowed to run on the device. Any value other than 1 is treated as 0.
HKEY_LOCAL_MACHINE\Security\Policies\Policies
DWord = 00001006 Data = Use the following-->
0 = Indicates that unsigned applications are not allowed to run on the device.
1 = Indicates that unsigned applications are allowed to run on the device.
Grant Manager Policy:
This policy contains a list of roles that are elevated to manager. If this role contains "UserAuth" then every action taken by the user has full administative access.
None: Indicates that only the manager is granted the Manager role.
OEM: Equipment manufacturer role.
Operator: Setting can be changed by the mobile operator.
Operator-TPS: Settings can be changed by a Wireless Application Protocol (WAP) Trusted Provisioning Server (TPS).
Manager: Settings can be changed by the manager or administrator.
UserAuth: Settings can be changed by an authenticated user.
UserUnAuth: Settings can be changed by anyone.
A specified role mask indicates system administrative privileges are given to the role mask specified.
HKEY_LOCAL_MACHINE\Security\Policies\Policies
DWord = 00001017 Data = Use the following-->
0 = None
2 = OEM
4 = Operator
6 = OEM, Operator
8 = Manager
10 = OEM, Manager
12 = Operator, Manager
14 = OEM, Operator, Manager
16 = UserAuth
18 = OEM, UserAuth
20 = Operator, UserAuth
22 = OEM, Operator, UserAuth
24 = Manager, UserAuth
26 = OEM, Manager, UserAuth
28 = Operator, Manager, UserAuth
30 = OEM, Operator, Manager, UserAuth
64 = UserUnAuth
66 = OEM, UserUnAuth
68 = Operator, UserUnAuth
70 = OEM, Operator, UserUnAuth
72 = Manager, UserUnAuth
74 = OEM, Manager, UserUnAuth
76 = Operator, Manager, UserUnAuth
78 = OEM, Operator, Manager, UserUnAuth
80 = UserAuth, UserUnAuth
82 = OEM, UserAuth, UserUnAuth
84 = Operator, UserAuth, UserUnAuth
86 = OEM, Operator, UserAuth, UserUnAuth
88 = Manager, UserAuth, UserUnAuth
90 = OEM, Manager, UserAuth, UserUnAuth
92 = Operator, Manager, UserAuth, UserUnAuth
94 = OEM, Operator, Manager, UserAuth, UserUnAuth
128 = Operator-TPS
130 = OEM, Operator-TPS
132 = Operator, Operator-TPS
134 = OEM, Operator, Operator-TPS
136 = Manager, Operator-TPS
138 = OEM, Manager, Operator-TPS
140 = Operator, Manager, Operator-TPS
142 = OEM, Operator, Manager, Operator-TPS
144 = UserAuth, Operator-TPS
146 = OEM, UserAuth, Operator-TPS
148 = Operator, UserAuth, Operator-TPS
150 = OEM, Operator, UserAuth, Operator-TPS
152 = Manager, UserAuth, Operator-TPS
154 = OEM, Manager, UserAuth, Operator-TPS
156 = Operator, Manager, UserAuth, Operator-TPS
158 = OEM, Operator, Manager, UserAuth, Operator-TPS
192 = UserUnAuth, Operator-TPS
194 = OEM, UserUnAuth, Operator-TPS
196 = Operator, UserUnAuth, Operator-TPS
198 = OEM, Operator, UserUnAuth, Operator-TPS
200 = Manager, UserUnAuth, Operator-TPS
202 = OEM, Manager, UserUnAuth, Operator-TPS
204 = Operator, Manager, UserUnAuth, Operator-TPS
206 = OEM, Operator, Manager, UserUnAuth, Operator-TPS
208 = UserAuth, UserUnAuth, Operator-TPS
210 = OEM, UserAuth, UserUnAuth, Operator-TPS
212 = Operator, UserAuth, UserUnAuth, Operator-TPS
214 = OEM, Operator, UserAuth, UserUnAuth, Operator-TPS
216 = Manager, UserAuth, UserUnAuth, Operator-TPS
218 = OEM, Manager, UserAuth, UserUnAuth, Operator-TPS
220 = Operator, Manager, UserAuth, UserUnAuth, Operator-TPS
222 = OEM, Operator, Manager, UserAuth, UserUnAuth, Operator-TPS
Unsigned Prompt Policy:
This policy indicates whether the user is prompted to accept or reject unsigned .cab, theme, .dll and .exe files.
HKEY_LOCAL_MACHINE\Security\Policies\Policies
DWord = 0000101a Data = Use the following-->
0 = Indicates user will be prompted.
1 = Indicates user will not be prompted.
Privileged Apps Policy:
The Privileged Apps policy setting specifies which security model is implemented on the device. Any value other than 1 is treated as 0.
HKEY_LOCAL_MACHINE\Security\Policies\Policies
DWord = 0000101b Data = Use the following-->
0 = Two Tier: Applications run normal and cannot access the protected registry keys or protected system APIs.
1 = One Tier: Applications run privileged and can access all registry keys and all system APIs.
Password Required Policy:
This policy indicates whether a password must be configured on the device.
HKEY_LOCAL_MACHINE\Security\Policies\Policies
DWord = 00001023 Data = Use the following-->
0 = Indicates that a password is required.
1 = Indicates that a password is not required. "Any value other than 0 will indicate no password required".
Desktop Unlock Policy:
This policy indicates how the desktop must handle authentication when the device is locked.
HKEY_LOCAL_MACHINE\Security\Policies\Policies
DWord = 00001025 Data = Use the following-->
0 = Indicates that the user must authenticate on the device if it is locked upon connect.
1 = Indicates the user can authenticate by using a PIN on the desktop.
If you find any errors please let me know.
I will update the list as more policies are discovered

-----------(Undefined)----------
"I dont know all possible settings for the following Policies yet"
UNAUTHENTICATED role is used for processing Homescreens
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"00001007"=dword:40
TPS Policy
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"00001008"=dword:1
Message Authentication Retry Number Policy
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"00001009"=dword:3
WAP Signed Message Policy
(default: SECROLE_PPG_AUTH | SECROLE_PPG_TRUSTED | SECROLE_OPERATOR_TPS)
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000100b"=dword:c80
SL Message Policy
(default: SECROLE_PPG_TRUSTED)
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000100c"=dword:800
SI Message Policy
(default: SECROLE_PPG_AUTH | SECROLE_PPG_TRUSTED)
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000100d"=dword:c00
Unauthenticated Message Policy
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000100e"=dword:40
OTA Provisioning Policy
(default: OPERATOR_TPS | SECROLE_PPG_TRUSTED | SECROLE_PPG_AUTH | SECROLE_TRUSTED_PPG | USER_AUTH)
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000100f"=dword:e90
WSP Push Policy
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"00001011"=dword:1
Grant User Auth Policy
(default: USER_AUTH)
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"00001018"=dword:10
Trust WAP Proxy Policy
(default: OPERATOR | OPERATOR_TPS | MANAGER)
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"00001019"=dword:8c
DRM Security Policy
(default SECROLE_PPG_AUTH | SECROLE_PPG_TRUSTED)
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"00001021"=dword:c00

it's a wonderful post. Very thanks

or you can use Security Configuration Manager

jsp_m said:
or you can use Security Configuration Manager
Click to expand...
Click to collapse
Where is this app?

http://forum.xda-developers.com/showpost.php?p=1488298&postcount=2
great app

Woops
I accidentally changed 00001001 to the value "2"
so am i just screwed now?
Can't change it back, access denied of course.

woops
yeah i don't know what happened but i disconnected ran EnableRAPI and reconnected it was changed back to 1. whew!

jsp_m said:
http://forum.xda-developers.com/showpost.php?p=1488298&postcount=2
great app
Click to expand...
Click to collapse
The page is no more. Got another link?

onestoploser said:
The page is no more. Got another link?
Click to expand...
Click to collapse
http://download.microsoft.com/download/e/e/0/ee050170-bb0e-492a-aa9e-8f82bc2e1c5e/Setup.msi

I'm having trouble with this. Whenever I try and change any of the entries I get "access denied" Am I doing something wrong?
only on these polocies. I can edit other registry entries. All I'm trying to do is set IE as my default browser as it was shipped full of Opera reg entries.
HELP PLEASE!

DWord = 00001005
Exellent information, but can't find the value for "40" on HKEY_LOCAL_MACHINE\Security\Policies\Policies
DWord = 00001005
Which is the value or definition for "40" on DWord = 00001005?
Thanks

joebi said:
I'm having trouble with this. Whenever I try and change any of the entries I get "access denied" Am I doing something wrong?
only on these polocies. I can edit other registry entries. All I'm trying to do is set IE as my default browser as it was shipped full of Opera reg entries.
HELP PLEASE!
Click to expand...
Click to collapse
I know the post is old but I get a new smartphone and I the same pb on some registries...
Any ideas?

While I was proceeding the syncronise between my PC and my device recently, I got very frequently about "access deny" problem. I know that when I did:
# Open the following key in the tree HKEY_LOCAL_MACHINE\Security\Policies\Policies\
# Click the value 00001001 and change it to 1
and can solve the problem, but then the value of 00001001 in the following code
HKEY_LOCAL_MACHINE\Security\Policies\Policies\
automatically changed back to "2" and every time I had to change it back manually. (seems to be every startup the value will be changed)
Do you have any opinions about what have happened? Thank you for your kind instruction.
Lee

ijlee said:
While I was proceeding the syncronise between my PC and my device recently, I got very frequently about "access deny" problem. I know that when I did:
# Open the following key in the tree HKEY_LOCAL_MACHINE\Security\Policies\Policies\
# Click the value 00001001 and change it to 1
and can solve the problem, but then the value of 00001001 in the following code
HKEY_LOCAL_MACHINE\Security\Policies\Policies\
automatically changed back to "2" and every time I had to change it back manually. (seems to be every startup the value will be changed)
Do you have any opinions about what have happened? Thank you for your kind instruction.
Lee
Click to expand...
Click to collapse
It could be that the setting for this key has been setup in a persistent way by another provxml file. I suggest you load a reg file everytime the ppc boots.

Have a similar problem
Hi all,
So I tried to install android the manual way earlier today (and also the Gen.Y dual Boot) and it just hung at some point (I went to lunch and it was stuck on same screen when I come back). So I done a soft reset intending to delete/uninstall and start again.
Now I cant install any cabs what so ever so have spent the last 3 hours trying to be able to install cabs again! Even my unsigned .exe's arnt working either. So I first tried remotely editing the registry, but I'm getting access denied each time I try to change HKEY_LOCAL_MACHINE\Security\Policies\Policies DWord = 00001001 to "1" instead, and in fact I cannot edit any keys in that subentry of Policies.
So I downloaded security configuration manager in a hope to do it that way, but it tries to load a cab file over when you try and make the change so that doesn't work either. So then i thought about signing a cab using the same program, but you need visual studio and a program called signtool.exe which i cant find anywhere on the internet.
I really reallllyyy don't want to hard reset my htc touch pro, I've never had to and don't intend on doing it now! Can anyone suggest where I can find that program or another way to unlock the security settings? Really need some more experienced advice on this and would be greatly appreciative of it

Related

Hi i currently have the WM6.1 in built client working with my SIP server the G711u codec works fine over HSPA but im curious to know if given G.729 would calls over GPRS be possible? Which bring me onto the main point If added to the registry and the codec placed in the approperate directory would this enable G.729 as a codec for the WM6.1 VoIP client:
; Configure ACM_G729 FormatTag
; Note that G729 frame_duration = 20ms in this example [HKEY_LOCAL_MACHINE\Comm\RTC\ACM\G729]
"PayloadType" = dword:12
"FrameDuration" = dword:A
"CodecRank" = dword:1
"Driver" = "g729.acm"
[HKEY_LOCAL_MACHINE\Comm\RTC\ACM\G729\WaveFormat]
"FormatTag" = dword:44
"Channels" = dword:1
"SamplesPerSec" = dword:1F40
"AvgBytesPerSec" = dword:3E8
"BlockAlign" = dword:A
"BitsPerSample" = dword:0
"bSize" = dword:2
; Configure ACM_G729 Prefix
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\CODEC_G729]
"Prefix"="ACM"
"Dll"="g729.acm"
; Cofigure Codec Preference
and for path:
[HKEY_LOCAL_MACHINE\Comm\RTC\Codec]
"PreferredAudioCodec"=dword:12 ; 0=pcmu, 12=729
"UsePreferredCodec"=dword:1
came from: http://msdn.microsoft.com/en-us/library/aa924754.aspx
Thanks
Dphi

dphiance said:
Hi i currently have the WM6.1 in built client working with my SIP server the G711u codec works fine over HSPA but im curious to know if given G.729 would calls over GPRS be possible? Which bring me onto the main point If added to the registry and the codec placed in the approperate directory would this enable G.729 as a codec for the WM6.1 VoIP client:
; Configure ACM_G729 FormatTag
; Note that G729 frame_duration = 20ms in this example [HKEY_LOCAL_MACHINE\Comm\RTC\ACM\G729]
"PayloadType" = dword:12
"FrameDuration" = dword:A
"CodecRank" = dword:1
"Driver" = "g729.acm"
[HKEY_LOCAL_MACHINE\Comm\RTC\ACM\G729\WaveFormat]
"FormatTag" = dword:44
"Channels" = dword:1
"SamplesPerSec" = dword:1F40
"AvgBytesPerSec" = dword:3E8
"BlockAlign" = dword:A
"BitsPerSample" = dword:0
"bSize" = dword:2
; Configure ACM_G729 Prefix
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\CODEC_G729]
"Prefix"="ACM"
"Dll"="g729.acm"
; Cofigure Codec Preference
and for path:
[HKEY_LOCAL_MACHINE\Comm\RTC\Codec]
"PreferredAudioCodec"=dword:12 ; 0=pcmu, 12=729
"UsePreferredCodec"=dword:1
came from: http://msdn.microsoft.com/en-us/library/aa924754.aspx
Thanks
Dphi
Click to expand...
Click to collapse
Maybe, if you have a g729.acm build for ARM/PocketPC. Do you?

Everybody knows those nice serials you can use to download ROMs from HTC. After some research about the serial numbers, here is how they are built :
2008 Serial Numbers :
Code:
HTUWWYYZZZZZ
HT = Vendor HTC
U = Year (8 = 2008)
WW = Week in a year
YY = Part Code
ZZZZZ : Identification Number (decimal)
2009 Serial Numbers :
Code:
HTYMDAABBBBB
HT = Vendor HTC
Y = Year (9 = 2009)
M = Month (hex 1...C = 1 - 12 months)
D = Day (hex 1...9A..Z = 1 - 31 days)
YY = Part Code
ZZZZZ : Identification Number (decimal)
Part Codes :
Code:
G3 = Sedna
G6 = Elfin
GH = Elf
K0 = Raphael
KW = Raphael C
K7 = Victor
EZ = Breeze
GN = Diamond
KT = Diamond MDA
BE = Prophet
EW = Prophet/PM300
F2 = Hermes
D6 = Blue Angel
GZ = Dream
FM = Athena
6G = Kaiser
G8 = Kaiser/Tytn II
DB = Typhoon
F2 = Melbourne/Census
BD = Charmer
N1 = Snap
L1 = Topaz
NW = Leo
LL = Rhodium
KD = Blackstone
GE = Polaris
KH = Jade
FS = Herald
FK = Trinity
EE = Wizard
GC = Nike
KN = Quartz
KF = Sapphire
HL = Supersonic
If you find further part codes not listed above, feel free to add them
Cya,
Viper BJK

My Touch Pro's part is "KW" (RAPH101)

Thanks .... is it a branded one ?

Nope, HTC Touch Pro T7274, with American 3G.

Update : Supersonic added

PL is the Code for Desire
HT041 means first april 2010?

Very interesting...

Don't mean to bring that back up but were having some trouble decoding the numbers on our Thunderbolts.. 1-9 a-z = 35 days
... were trying to make a database of the dates phones were made for bricking... if you have any insight on this please help.

Interesting
Very interesting indeed

viperbjk said:
Everybody knows those nice serials you can use to download ROMs from HTC. After some research about the serial numbers, here is how they are built :
2008 Serial Numbers :
Code:
HTUWWYYZZZZZ
HT = Vendor HTC
U = Year (8 = 2008)
WW = Week in a year
YY = Part Code
ZZZZZ : Identification Number (decimal)
2009 Serial Numbers :
Code:
HTYMDAABBBBB
HT = Vendor HTC
Y = Year (9 = 2009)
M = Month (hex 1...C = 1 - 12 months)
D = Day (hex 1...9A..Z = 1 - 31 days)
YY = Part Code
ZZZZZ : Identification Number (decimal)
Part Codes :
Code:
G3 = Sedna
G6 = Elfin
GH = Elf
K0 = Raphael
KW = Raphael C
K7 = Victor
EZ = Breeze
GN = Diamond
KT = Diamond MDA
BE = Prophet
EW = Prophet/PM300
F2 = Hermes
D6 = Blue Angel
GZ = Dream
FM = Athena
6G = Kaiser
G8 = Kaiser/Tytn II
DB = Typhoon
F2 = Melbourne/Census
BD = Charmer
N1 = Snap
L1 = Topaz
NW = Leo
LL = Rhodium
KD = Blackstone
GE = Polaris
KH = Jade
FS = Herald
FK = Trinity
EE = Wizard
GC = Nike
KN = Quartz
KF = Sapphire
HL = Supersonic
If you find further part codes not listed above, feel free to add them
Cya,
Viper BJK
Click to expand...
Click to collapse
for ZZZZZ
it it was found that actually it is "CC-ZZZ"
CC is for country code
i only know that
46 = Germany
37 = Dubai
Please add more country codes...

The first two characters actually mean the place of manufacture.
SZ = Shenzhen, China
SH = Shanghai, China
HT = Hsinchu, Taiwan
CH = Wuhan, China
A pic of a HTC Desire made in Shanghai can be found here:
http://www.rei3.com/archives/8416.html

The Shooter's (CDMA Evo 3D's) part code is HX

That's cool info. Thanks for the insight guys.
Sent from my Transformer TF101 using Tapatalk

good info))) would have to look over and add it)))

MB139PK41124???

my Serial starts with FA does anyone know where this might be? while one i bought for my partner is HT

Hi all.
I search for an MSN Messenger full HTTP (for WAP connexion) on my smartphone.
No thanks for HiMSN or other, I don't and never enter my account on his website.
I find an WindowsLiveMessenger.apk, and when I docompact it I found, it's probably work only on Bytel network.
I'm on SFR.
See the file : /WindowsLiveMessenger.apk/res/raw/app_param.txt
Code:
#Application Parameter URL
#---URL---
GATE DEMO http://85.31.202.156:80/appparam/sanity_all
#protocol = http
#URL = 85.31.202.156
#port = 80
#path = /appparam/sanity_all
#Emulo /wifi
#protocol = http
#URL = 10.20.20.7
#port = 31000
#path = /pub/nocir
#Tel
#protocol = http
#URL = 85.31.202.155
#port = 80
#path = /pub
#PPE bytel
#protocol = http
#URL = sb01.qnitabxn.mpit.ppe.miyowa.net
#port = 80
#path = /
#Special QA
#protocol = http
#URL = 85.31.202.155
#port = 80
#path = /qandroid
#Prod Bytel
protocol = http
URL = sb01.qnitabxn.mpit.prd.miyowa.net
port = 80
path = /
# 3UK chez eux phase 2
#protocol = http
#URL = mobile.three.co.uk
#port = 80
#path = /966_accs/android/cir/
#Prod 3 phase 1
#protocol = http
#URL = sb01.iwgttjcx.mpit.prd.miyowa.net
#port = 80
#path = /
#PPE 3 phase 1
#protocol = http
#URL = sb01.iwgttjcx.mpit.ppe.miyowa.net
#port = 80
#path = /
#PPE NRJ
#protocol = http
#URL = msnnrjppe.miyowa.net
#port = 80
#path = /it5/pub
#Prod NRJ
#protocol = http
#URL = msnnrjpr.miyowa.net
#port = 80
#path = /pub/
#TEST CHAMPI
#protocol = http
#URL = sb01.qpzgxtbx.mpit.ppe.miyowa.net
#port = 80
#path = /
#TEST SMS CIR 3UK
#protocol = http
#URL = 85.31.202.155
#port = 80
#path = /pub
#Application Parameter parameters
#---PARAMETERS---
#PhoneID = brand_model
#PhoneID = Samsung_I7500
#PhoneID = Bravo
# Phone ID = Version OS, Nom du mobile (I7500)
ApplicationID = IT5_Miyowa_3.01
Version = 0.2
Language = FRA
DeviceID = Android
#Application Parameter header HTML
#---HEADERS---
OsVersion = 1.5
Content-Type = application/x-www-form-urlencoded
connection = close
### Emulateur ###
#MSISDN_KEY = msisdn,X-Up-Calling-Line-Id
### Bytel ###
#MSISDN_KEY = msisdn,X-Msid
### 3UK not use in phase 2 ###
#MSISDN_KEY = X-NMCA-IDENTITY
#TEST CHAMPI
#MSISDN_KEY = X_MIYO_IMSI
#MSISDN_VALUE = QOS7777
#MSISDN_VALUE = 00447853082623
#MSISDN_VALUE = zte
Roaming-Test = true
#Roaming-Test = false
test-is-using-3G = true
#test-is-using-3G = false
#show-stay-alerted = true
show-stay-alerted = false
RessourcesLanguage = FR
typeofoffer = A
X-Nokia-BEARER = UMTS
roamingoutflag = 0
#Informations
MaxPDU = 16384
FileEncondingType = 0
ApplicationVersion = 0.2.33.0
IS_BIG_SCREEN = true
#IS_BIG_SCREEN = false
#SHOW_POPUP_FIRST_SIGN_IN = true
SHOW_POPUP_FIRST_SIGN_IN = false
#SHOW_TABS_IN_LANDSCAPE_MODE = true
SHOW_TABS_IN_LANDSCAPE_MODE = false
#TestMCCMNC = true
TestMCCMNC = false
#3UK MCC - MNC
MCCMNC = 23420,23410,23433,27205,24002,24004,23806,22299,23210,50506,45403,23594
Do you meen hack this APK to connect to MSN with any phone operators ?
Or do you know and MSN client full HTTP, and I don't must to register my account on a stupid website ?
Thanks.

Why on earth, would you rather use the web version than the HiMSN?
As far as I have experienced, HIMsn/MSNTalk works just fine.
Is there some reason, why you would not like to use an app from the market?

May you share wth us..i mean im searchin a WindowsLiveMessenger .apk non-javabased version..n cud not find yet...cuz dunno why java based one doesnt work ..cannot connect da server..i need a regular apk as windows live...

In case you need to know how to poll GPIO values from photon, here is a small how-to:
First of all, read THIS:
http://htc-linux.org/wiki/index.php?title=HaRET_Documentation#Polling_GPIOs
To disable automatic launch of Android when you execute HarET, you must rename your file "startup.txt" to "default.txt"
The issue is, when you poll for GPIOs with Haret, you got a numeric value that does not match with GPIOs in Linux (board-photon.h)
To translate "HarET GPIO" to "Linux GPIO", here is a trick:
Haret gives you this line:
009.179 GPIOS 92f00808(117)=300100
Click to expand...
Click to collapse
Take the number between parenthesis: 117
Divide it by 32:
117/32 = 3, rest = 21
3 is the GPIO bank:
bank0 = 0 to 15
bank1 = 16 to 42
bank2 = 43 to 67
bank3 = 68 to 94
bank4 = 95 to 106
bank5 = 107 to 121
in our example, bank3 starts at value 68, so the Linux GPIO is:
68 + 21(rest of division) = 89
note: if the bank number is higher than 5, it means it is the following bank, or the one after. in this case, remove 6 or 12 to the bank number so you have a value between 0 and 5, and do the normal computation.

I must to say THANK YOU!

hmm I not understand (rest) I got 3,65625 (bank 3, rest 65626)
r0bin said:
117/32 = 3, rest = 21
Click to expand...
Click to collapse
Also next situation:
057.215 GPIOS 92f0083c(313)=61c8102
9,78125 (bank 9, rest 78125)

munjeni said:
hmm I not understand (rest) I got 3,65625 (bank 3, rest 65626)
Also next situation:
057.215 GPIOS 92f0083c(313)=61c8102
9,78125 (bank 9, rest 78125)
Click to expand...
Click to collapse
lol
on my sample, another way to say it:
117/32 = (3 * 32) + 21
or:
117/32 = 3.65625, you take the 3, rest 0.65625 * 32 = 21
in your case:
303/32 = 9.78125, you take the 9, rest 0.78125 * 32 = 25
9 is too big, remove 6 => it's bank3
bank3 = 68+25 = 93
in board-photon.h, it is defined like:
LIBERTY_GPIO_LS_EN 93
in the code (board-photon.c) it seems it's the GPIO for power

thanks, understand now \o/

Hi,
I got slightly different format for GPIOS.
Please refer to here
http://pastebin.com/xr4p3cd8
How to I convert them?
Thanks in advance

Hi,
I've been looking for a tool or script to replace hex sequence in binary file in Windows. Indeed, i found this script :
Code:
Imports System.Runtime.CompilerServices
Imports System.IO
Public Class FinduReplaceHex
Private Shared ReadOnly FindHex As Byte() = {&H75, &HF6, &HF3}
Private Shared ReadOnly ReplaceHex As Byte() = {&HA2, &HE3, &H4B}
<MethodImpl(MethodImplOptions.NoInlining)> Private Shared Function DP(sequence As Byte(), position As Integer) As Boolean
If position + FindHex.Length > sequence.Length Then
Return False
End If
For i As Integer = 0 To FindHex.Length - 1
If FindHex(i) <> sequence(position + i) Then
Return False
End If
Next
Return True
End Function
Private Sub Patch_Click(sender As Object, e As EventArgs) Handles Patch.Click
Dim DT As String = Environment.GetFolderPath(Environment.SpecialFolder.Desktop)
Dim FD As Byte() = File.ReadAllBytes(DT & "\App.dll")
For F As Integer = 0 To FD.Length - 1
If Not DP(FD, F) Then
Continue For
End If
For R As Integer = 0 To FindHex.Length - 1
FD(F + R) = ReplaceHex®
Next
Next
If System.IO.File.Exists(DT & "\App.dll") Then
System.IO.File.Move(DT & "\App.dll", DT & "\App.dll.backup")
File.WriteAllBytes(DT & "\App Method 3.dll", FD)
Else
'Write Other Codes
End If
End Sub
End Class
The only problem is that I want to be able to use wildcards like this :
Search for F4 B3 ?? 12 and replace F4 BE 65 EA
Thanks in advance