Database Info

Disable Unsigned Security Warning in ROM

I am having trouble disabling the security policy in windows mobile 6.0 for the tilt. I have went through all the provxml files as well as all rgu files and changed the valued of HKLM_Security_Policies_Policies_0000101a to 1. Tried reflashing however once it booted The warning still poped up. I finally took the default.hv file and edited manually after build OS was finished by removing from the temp folder editing it and then dropping it back in. After it build the rom and then reflash its still there. So I have tried just about everything to disable this file the only other thing I can think of is Im missing a provxml file somewhere or I missing it because 0000101a is written in possibly a shortcut format. I have all analyzed all cab files to see if this change was being forced however to no avail. Perhaps this means something:
mxipupdate_oemoperators_104.provxml
<!-- Security Policy -->
<characteristic type="SecurityPolicy">
<parm name="2" value="0"/>
<parm name="4097" value="1"/>
<parm name="4101" value="16"/>
<parm name="4102" value="1"/>
<parm name="4103" value="64"/>
<parm name="4104" value="1"/>
<parm name="4105" value="5"/>
<parm name="4108" value="2112"/>
<parm name="4109" value="3136"/>
<parm name="4110" value="64"/>
<parm name="4111" value="3732"/>
<parm name="4113" value="1"/>
<parm name="4119" value="180"/>
<parm name="4120" value="16"/>
<parm name="4121" value="140"/>
<parm name="4122" value="0"/>
<parm name="4124" value="1"/>
<parm name="4141" value="4096"/>
<parm name="4142" value="3200"/>
<parm name="4143" value="4096"/>
</characteristic>
Can anyone please tell me if this information above located in a provxml file is changing the value to 0 on policies 0000101a?

hey man,
just use the package I just uploaded. It works fine on every single ROM I've ever cooked

Will Give It a Try. Hope this works lol.

HURRAY
It worked Sir. Thank you very much!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Cant edit proxy!!

few weeks ago, i had my p527's touchscreen dead.. neway loads of keys hav been very useful to operate the device.. but i cannot add or edit proxy!! i want to edit http, wap, wap socket all of them but cant. i keep on pressing the scroller key but nothin happens... i suppose it needs a touch tap over them... i had wm6.5.. then installed 6.1.. nd now 6.0 but the problem exists.
i tried to make xml file nd import it but failed.. through xml, i could only assign to wap proxy.. http nd wap socket stays empty!!
here's the xml..
Code:
<!--BPL-->
<wap-provisioningdoc>
<characteristic type="CM_Networks">
<characteristic type="BPL WAP Settings">
<parm name="DestId" value="{FB30C2F9-3949-42ff-875D-09E2B8A6A6B8}" />
</characteristic>
<characteristic type="BPL MMS Settings">
<parm name="DestId" value="{6C02DE52-0ADD-4057-8542-E68DE9797D19}" />
</characteristic>
</characteristic>
<characteristic type="CM_GPRSEntries">
<characteristic type="BPL GPRS WAP">
<parm name="DestId" value="{FB30C2F9-3949-42ff-875D-09E2B8A6A6B8}" />
<parm name="UserName" value="mobileno" />
<parm name="Password" value="mmsc" />
<parm name="Phone" value="~GPRS!mizone" />
<parm name="SwCompression" value="0" />
<parm name="IpHeaderCompression" value="0" />
<parm name="Enabled" value="1" />
<characteristic type="DevSpecificCellular">
<parm name="BearerInfoValid" value="1" />
<parm name="GPRSInfoValid" value="1" />
<parm name="GPRSInfoProtocolType" value="2" />
<parm name="GPRSInfoL2ProtocolType" value="PPP" />
<parm name="GPRSInfoAccessPointName" value="mizone" />
<parm name="GPRSInfoAddress" value="" />
<parm name="GPRSInfoDataCompression" value="1" />
<parm name="GPRSInfoHeaderCompression" value="1" />
<parm name="GPRSInfoParameters" value="" />
</characteristic>
</characteristic>
<characteristic type="BPL GPRS MMS">
<parm name="DestId" value="{6C02DE52-0ADD-4057-8542-E68DE9797D19}" />
<parm name="UserName" value="mobileno" />
<parm name="Password" value="mmsc" />
<parm name="Phone" value="~GPRS!mizone"/>
<parm name="SwCompression" value="0" />
<parm name="IpHeaderCompression" value="0" />
<parm name="Enabled" value="1" />
<characteristic type="DevSpecificCellular">
<parm name="BearerInfoValid" value="1" />
<parm name="GPRSInfoValid" value="1" />
<parm name="GPRSInfoProtocolType" value="2" />
<parm name="GPRSInfoL2ProtocolType" value="PPP" />
<parm name="GPRSInfoAccessPointName" value="mizone" />
<parm name="GPRSInfoAddress" value="" />
<parm name="GPRSInfoDataCompression" value="1" />
<parm name="GPRSInfoHeaderCompression" value="1" />
<parm name="GPRSInfoParameters" value="" />
</characteristic>
</characteristic>
</characteristic>
<characteristic type="Registry">
<characteristic type="HKLM\SoftWare\Jataayu\MMS\Profiles">
<parm name="ActiveProfile" value="BPL" datatype="string" />
</characteristic>
<characteristic type="HKLM\SoftWare\Jataayu\MMS\Profiles\BPL">
<parm name="Encoding" value="0" datatype="integer" />
<parm name="Port" value="9401" datatype="integer" />
<parm name="IP Address" value="10.0.0.10" datatype="string" />
<parm name="Gateway" value="2" datatype="integer" />
<parm name="Data Connections" value="{6C02DE52-0ADD-4057-8542-E68DE9797D19}" datatype="string" />
<parm name="MMSC URL" value="http://mms.bplmobile.com:8080" datatype="string" />
</characteristic>
</characteristic>
<characteristic type="CM_ProxyEntries">
<characteristic type="HTTP-{FB30C2F9-3949-42ff-875D-09E2B8A6A6B8}">
<parm name="DestId" value="{436EF144-B4FB-4863-A041-8F905A62C572}" />
<parm name="SrcId" value="{FB30C2F9-3949-42ff-875D-09E2B8A6A6B8}" />
<parm name="Proxy" value="10.0.0.10:9401" />
<parm name="Type" value="2" />
<parm name="Enabled" value="1" />
</characteristic>
<characteristic type="WAP-{FB30C2F9-3949-42ff-875D-09E2B8A6A6B8}">
<parm name="DestId" value="{7022E968-5A97-4051-BC1C-C578E2FBA5D9}" />
<parm name="SrcId" value="{FB30C2F9-3949-42ff-875D-09E2B8A6A6B8}" />
<parm name="Proxy" value="10.0.0.10:9401" />
<parm name="Type" value="2" />
<parm name="Enabled" value="1" />
</characteristic>
<characteristic type="WAP-{6C02DE52-0ADD-4057-8542-E68DE9797D19}">
<parm name="DestId" value="{7022E968-5A97-4051-BC1C-C578E2FBA5D9}" />
<parm name="SrcId" value="{6C02DE52-0ADD-4057-8542-E68DE9797D19}" />
<parm name="Proxy" value="10.0.0.10:9401" />
<parm name="Type" value="2" />
<parm name="Enabled" value="1" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
i need proxy address 10.0.0.10 nd port 9401 to b assigned in fields of proxy advanced....
pls help!!

seems to b a wrong forum!!

I can't delete Google Maps via XML Provisioning

I need to delete Google Maps via XML Provisioning, I have run the following in .Cab files.
The following bit works but I'm not sure if it is sufficient to give me the priviliges I want......
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\Security\Policies\Policies">
<parm name="0000100f" value="3728" datatype="integer" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
...... and this bit doesn't work.......
<wap-provisioningdoc>
<characteristic type="UnInstall">
<characteristic type="\Program Files\GoogleMaps\GoogleMaps.exe">
<parm name="uninstall" value="1"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
any help will be greatly appreciated....

[Q] HTC Trophy NZ

If there's anybody on here with an HTC Trophy from NZ (Vodafone) can you please tell me the version number? I accidentally ran a registry file that wrote over the default value since it was designed for an HD7.
The value below needs to be changed but the rest can be copied and saved as a CustClear.provxml file in order to prevent relocking.
In return dumping values that will aid anyone who stuffs up their trophy:
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\Software\HTC\operatorpkg">
<parm name="Version" value="7.1.401.10291" datatype="string" />
</characteristic>
<characteristic type="HKLM\System\Platform\DeviceTargetingInfo">
<parm name="OemName" value="HTC" datatype="string" />
<parm name="MODeviceName" value="7 Trophy T8686" datatype="string" />
<parm name="OEMDeviceName" value="Spark" datatype="string" />
</characteristic>
<characteristic type="HKLM\Ident">
<parm name="FriendlyName" value="HTC Trophy" datatype="string" />
</characteristic>
<characteristic type="HKLM\Software\Microsoft\DeviceReg">
<parm name="PortalUrlProd" value="https://developerservices.unlock.me/Services/WindowsPhoneRegistration.svc/01/2010" datatype="string" />
<parm name="PortalUrlInt" value="https://developerservices.unlock.me/Services/WindowsPhoneRegistration.svc/01/2010" datatype="string" />
</characteristic>
<characteristic type="HKLM\Software\Microsoft\DeviceReg\Install">
<parm name="MaxUnsignedApp" value="2147483647" datatype="integer" />
</characteristic>
<characteristic type="HKLM\Comm\BCMSDDHD1\Parms">
<parm name="11nModeDisable" value="0" datatype="integer" />
</characteristic>
</characteristic>
</wap-provisioningdoc>

iamcarl4ever said:
If there's anybody on here with an HTC Trophy from NZ (Vodafone) can you please tell me the version number? I accidentally ran a registry file that wrote over the default value since it was designed for an HD7.
The value below needs to be changed but the rest can be copied and saved as a CustClear.provxml file in order to prevent relocking.
In return dumping values that will aid anyone who stuffs up their trophy:
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\Software\HTC\operatorpkg">
<parm name="Version" [COLOR="Red"]value="7.1.401.10291"[/COLOR] datatype="string" />
</characteristic>
<characteristic type="HKLM\System\Platform\DeviceTargetingInfo">
<parm name="OemName" value="HTC" datatype="string" />
<parm name="MODeviceName" value="7 Trophy T8686" datatype="string" />
<parm name="OEMDeviceName" value="Spark" datatype="string" />
</characteristic>
<characteristic type="HKLM\Ident">
<parm name="FriendlyName" value="HTC Trophy" datatype="string" />
</characteristic>
<characteristic type="HKLM\Software\Microsoft\DeviceReg">
<parm name="PortalUrlProd" value="https://developerservices.unlock.me/Services/WindowsPhoneRegistration.svc/01/2010" datatype="string" />
<parm name="PortalUrlInt" value="https://developerservices.unlock.me/Services/WindowsPhoneRegistration.svc/01/2010" datatype="string" />
</characteristic>
<characteristic type="HKLM\Software\Microsoft\DeviceReg\Install">
<parm name="MaxUnsignedApp" value="2147483647" datatype="integer" />
</characteristic>
<characteristic type="HKLM\Comm\BCMSDDHD1\Parms">
<parm name="11nModeDisable" value="0" datatype="integer" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
Click to expand...
Click to collapse
Hey there,
Version number should be 7.1.179.10071 (Vodafone NZ HTC Trophy)

[Q] provxml file to configure MMS on Samsung

I found this thread where someone with an HTC device used a provxml method to configure the MMS settings.
http://forum.xda-developers.com/showthread.php?t=1223925
I am wondering if the same method could be used for my focus. I have an unloked device, but my carrier (Bell Mobility) does not offer the focus.
I have tried all the methods I can find eg. rest the ADC etcetera, but the AT&T settings are still in the register.
I can find the proper settings from the Bell web site, just not sure how to get them in the correct place.
Thanks in advance
Below is the code he used.
Code:
<wap-provisioningdoc>
<characteristic type="NAPDEF">
<characteristic type="internet_line" mwid="1">
<parm name="BEARER" value="GSM-GPRS"/>
<parm name="NAP-ADDRTYPE" value="APN"/>
<parm name="NAP-ADDRESS" value="internet"/>
<characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP"/>
<parm name="AUTHNAME" value="telenor"/>
<parm name="AUTHSECRET" value="gprs"/>
</characteristic>
<parm name="INTERNET" value="1"/>
</characteristic>
<characteristic type="mms_line" mwid="1">
<parm name="BEARER" value="GSM-GPRS"/>
<parm name="NAP-ADDRTYPE" value="APN"/>
<parm name="NAP-ADDRESS" value="mms"/>
<characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP"/>
<parm name="AUTHNAME" value=""/>
<parm name="AUTHSECRET" value=""/>
</characteristic>
</characteristic>
</characteristic>
<characteristic type="PXLOGICAL">
<characteristic type="mms_line-PROXY" mwid="1">
<parm name="PROXY-ID" value="mms_line-PROXY" />
<parm name="DOMAIN" value="mms.telenor.rs"/>
<characteristic type="PXPHYSICAL">
<characteristic type="mms_line-PROXY" mwid="1">
<parm name="TO-NAPID" value="mms_line"/>
<parm name="PXADDR" value="217.65.192.33"/>
<characteristic type="PORT">
<parm name="PORTNBR" value="8080"/>
<parm name="SERVICE" value="80"/>
</characteristic>
</characteristic>
</characteristic>
</characteristic>
</characteristic>
<characteristic type="APPLICATION">
<parm name="APPID" value="w4"/>
<parm name="NAME" value="MMS"/>
<parm name="ADDR" value="http://mms.telenor.rs/servlets/mms"/>
<parm name="TO-PROXY" value="mms_line-PROXY"/>
<parm name="TO-NAPID" value="mms_line"/>
<parm name="MS" value="600"/>
</characteristic>
</wap-provisioningdoc>
Solution from the Laquox post:
<wap-provisioningdoc>
<!-- *** COMMENTO *** -->
<characteristic type="Registry">
<characteristic type="HKLM\System\AutoDataConfig">
<parm name="RunADC" value="1" datatype="integer" />
<parm name="ConfigurationStatus" value="0" datatype="integer" />
<parm name="Attempt" value="0" datatype="integer" />
<parm name="MaxAttemptsAllowed" value="3" datatype="integer" />
</characteristic>
</characteristic>
</wap-provisioningdoc>

Take a look at this thread basically in the end all you have to do is search the marketplace for a app called "Network Profile" under samsung zone and it fixes Samsung mms problems. It's simply because when updating to mango it has to reset a certain flag. In particular
Code:
[HKEY_LOCAL_MACHINE\System\AutoDataConfig]
"RunADC"=dword:1

Laquox said:
Take a look at this thread basically in the end all you have to do is search the marketplace for a app called "Network Profile" under samsung zone and it fixes Samsung mms problems. It's simply because when updating to mango it has to reset a certain flag. In particular
Code:
[HKEY_LOCAL_MACHINE\System\AutoDataConfig]
"RunADC"=dword:1
Click to expand...
Click to collapse
Thanks for the reply, but as far as I know this app only works if Samsung has created a profile for your network. In Canada where I am the only network profile is for Rogers. I am on Bell. So for users on the other carriers it will not work as well.
I have been able to set the ADC flag using Samsung tools. This gets the data working, but not MMS.
I have seen others use the provxml method to make this work. I plan on attempting this later this week.
Thanks again.

Oister Mobile
Allrigth, now I've made this work for my Oister subscription;
I renamed the attached xml to *.txt and e-mailed it to my mail on the phone, opened it in Word and saved to phone.
Then used "WP7 Root Tools" to copy file from "My Documents" to "provxml" and renamed to *.xml.
Then opened Diagnostics as mentioned in one of my earlier posts and installed. I think this is the easiest way to do this.
Send me a PM if you need help making a xml for your carrier, and I'll see what I can do...

After A LOTTTTT of trial and error I manage to have a ProvXML that is valid and working for my samsung focus (1st gen bought from rogers) to have MMS working with Fido.
I used this method to be able to install all the tools I needed:
http://windowsphonehacker.com/windowbreak/
I tried doing the changes with WP7 Root tools but didn't manage to achieve anything.
Then I used this tool http://forum.xda-developers.com/showthread.php?t=1238519
along with the Windows Phone Tools (located here: http://wptools.codeplex.com/)
So in order:
1. Root your phone with windowbreak.
2. Install the Windows Phone Tools
3. Install the ProvXML Diag tool
4. Upload your ProvXML files to the iso store of the DiagTool with the Windows Phone Tools software.
5. Run the Diag Tool and go to the Iso store, fire the context menu on the xml file you uploaded, select execute, and reboot your phone.
It's working for me using the xml file attached to this message!
Good luck!